Method and/or system for positioning of a mobile device

ABSTRACT

Methods and systems provide location services for user equipment (UE) devices in a radio access network (RAN) such as a Fifth Generation (5G) RAN. An example method of locating a user equipment (UE) at a location server includes exchanging one or more first signaling messages with the UE, and exchanging one or more second signaling messages with a location server associated with a core network. In the example method, the location server is integrated with a base station or a success point.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.15/273,305, filed Sep. 22, 2016, entitled “Method and/or System ForPositioning of a Mobile Device,” which claims the benefit of U.S.Provisional Application No. 62/336,500, entitled “Method and/or Systemfor Positioning” filed May 13, 2016; this application is also related toU.S. patent application Ser. No. 15/975,414, filed May 9, 2018, entitled“Method and/or System For Positioning of a Mobile Device,” each of theseapplications are assigned to the assignee hereof and are expresslyincorporated in their entirety herein by reference.

BACKGROUND

Field

Subject matter disclosed herein relates to estimation of a location of amobile device.

Information

The location of a mobile device, such as a cellular telephone, may beuseful or essential to a number of applications including emergencycalls, navigation, direction finding, asset tracking and Internetservice. The location of a mobile device may be estimated based oninformation gathered from various systems. In a cellular networkimplemented according to 4G (also referred to as Fourth Generation) LongTerm Evolution (LTE) radio access, for example, a base station maytransmit a positioning reference signal (PRS). A mobile device acquiringPRSs transmitted by different base stations may deliver signal-basedmeasurements to a location server, which may be part of an EvolvedPacket Core (EPC), for use in computing a location estimate of themobile device using observed time difference of arrival (OTDOA)techniques. Alternatively, a mobile device may compute an estimate ofits location using OTDOA techniques.

In cellular networks implementing more spectrum efficient and higherbandwidth radio interfaces than LTE (e.g. such as 5G), positioningmethods similar to those used for LTE may be defined and deployed (e.g.OTDOA) as well as new positioning methods (e.g. based on newcharacteristics and signals for a 5G radio interface). The similarand/or new positioning methods may provide performance improvements overthose used for 4G—e.g. higher accuracy, reduced latency and/or highercapacity. In order to fully exploit these performance improvementswithout undue constraint and maximize the benefits to both users andnetwork operators, changes may be needed to location solutions employedby networks (e.g. changes to network architecture, protocols andpositioning related procedures). Such changes may be used in both newer5G (also referred to as Fifth Generation) networks and in legacy 3G(also referred to as 3.0 G) and 4G networks, for example.

SUMMARY

Briefly, one particular implementation is directed to a method oflocating a user equipment (UE) at a location server function associatedwith a radio access network, comprising: exchanging one or more firstsignaling messages with the UE, the one or more first signaling messagescomprising: (i) a location measurement obtained by the UE, the locationserver function enabled to determine a location estimate for the UEbased at least in part on the location measurement; (ii) a request sentto the UE for the location measurement; (iii) assistance data sent tothe UE, the assistance data assisting the UE to obtain the locationmeasurement; or (iv) a combination thereof; and exchanging one or moresecond signaling messages with a location server associated with a corenetwork, the one or more second signaling messages comprising locationinformation for the UE, a request for the location information for theUE, a location configuration for the UE, a request for the locationconfiguration for the UE, a location context for the UE, a request forthe location context for the UE, or a combination thereof.

Another particular implementation is directed to a method of supportinglocation services at a user equipment (UE), comprising exchanging one ormore first signaling messages with a location server function associatedwith a radio access network, the one or more first signaling messagescomprising: (i) a first location measurement obtained by the UE, thelocation server function enabled to determine a an estimate location ofthe UE based at least in part on the first location measurement; (ii) arequest received by the UE for the first location measurement; (iii)first assistance data received by the UE, the first assistance dataassisting the UE to obtain the first location measurement; or (iv) acombination thereof; and exchanging one or more second signalingmessages with a location server associated with a core network, the oneor more second signaling message comprising a second locationmeasurement obtained by the UE, a request received by the UE for thesecond location measurement, second assistance data received by the UE,the second assistance data assisting the UE to obtain the secondlocation measurement, or a combination thereof.

Another particular implementation is directed to a location serverfunction associated with a radio access network for locating a userequipment (UE), comprising: a communication interface to transmit andreceive signaling messages; and one or more processors configured toexchange one or more first signaling messages with the UE through thecommunication interface, the one or more first signaling messagescomprising: (i) a location measurement obtained by the UE, the locationserver function enabled to determine a location estimate for the UEbased at least in part on the location measurement; (ii) a request sentto the UE for the location measurement; (iii) assistance data sent tothe UE, the assistance data assisting the UE to obtain the locationmeasurement; or (iv) a combination thereof; and exchange one or moresecond signaling messages with a location server associated with a corenetwork through the communication interface, the one or more secondsignaling messages comprising location information for the UE, a requestfor the location information for the UE, a location configuration forthe UE, a request for the location configuration for the UE, a locationcontext for the UE, a request for the location context for the UE, or acombination thereof.

Another particular implementation is directed to a user equipment (UE)to support location services, comprising: a wireless transceiver totransmit signaling messages to and receive signaling messages from acommunication network; and one or more processors configured to:exchange one or more first signaling messages with a location serverfunction associated with a radio access network through the wirelesstransceiver, the one or more first signaling messages comprising: (i) afirst location measurement obtained by the UE, the location serverfunction enabled to determine a an estimate location of the UE based atleast in part on the first location measurement; (ii) a request receivedby the UE for the first location measurement; (iii) first assistancedata received by the UE, the first assistance data assisting the UE toobtain the first location measurement; or (iv) a combination thereof;and exchange one or more second signaling messages with a locationserver associated with a core network through the wireless transceiver,the one or more second signaling message comprising a second locationmeasurement obtained by the UE, a request received by the UE for thesecond location measurement, second assistance data received by the UE,the second assistance data assisting the UE to obtain the secondlocation measurement, or a combination thereof.

Another particular implementation is directed to a non-transitorystorage medium comprising computer-readable instructions stored thereonwhich are executable by one or more processors of a location serverfunction associated with a radio access network for locating a userequipment (UE) to: exchange one or more first signaling messages withthe UE, the one or more first signaling messages comprising: (i) alocation measurement obtained by the UE, the location server functionenabled to determine a location estimate for the UE based at least inpart on the location measurement; (ii) a request sent to the UE for thelocation measurement; (iii) assistance data sent to the UE, theassistance data assisting the UE to obtain the location measurement; or(iv) a combination thereof; and exchange one or more second signalingmessages with a location server associated with a core network, the oneor more second signaling messages comprising location information forthe UE, a request for the location information for the UE, a locationconfiguration for the UE, a request for the location configuration forthe UE, a location context for the UE, a request for the locationcontext for the UE, or a combination thereof.

Another particular implementation is directed to a location serverfunction associated with a radio access network for locating a userequipment (UE) comprising: means for exchanging one or more firstsignaling messages with the UE, the one or more first signaling messagescomprising: (i) a location measurement obtained by the UE, the locationserver function enabled to determine a location estimate for the UEbased at least in part on the location measurement; (ii) a request sentto the UE for the location measurement; (iii) assistance data sent tothe UE, the assistance data assisting the UE to obtain the locationmeasurement; or (iv) a combination thereof; and means for exchanging oneor more second signaling messages with a location server associated witha core network, the one or more second signaling messages comprisinglocation information for the UE, a request for the location informationfor the UE, a location configuration for the UE, a request for thelocation configuration for the UE, a location context for the UE, arequest for the location context for the UE, or a combination thereof.

Another particular implementation is directed to a non-transitorystorage medium comprising computer-readable instructions stored thereonwhich are executable by one or more processors of method of at a userequipment (UE) supporting location services to: exchange one or morefirst signaling messages with a location server function associated witha radio access network, the one or more first signaling messagescomprising: (i) a first location measurement obtained by the UE, thelocation server function enabled to determine an estimate location ofthe UE based at least in part on the first location measurement; (ii) arequest received by the UE for the first location measurement; (iii)first assistance data received by the UE, the first assistance dataassisting the UE to obtain the first location measurement; or (iv) acombination thereof; and exchange one or more second signaling messageswith a location server associated with a core network, the one or moresecond signaling message comprising a second location measurementobtained by the UE, a request received by the UE for the second locationmeasurement, second assistance data received by the UE, the secondassistance data assisting the UE to obtain the second locationmeasurement, or a combination thereof.

Another particular implementation is directed to a user equipment (UE)supporting location services comprising: means for exchanging one ormore first signaling messages with a location server function associatedwith a radio access network, the one or more first signaling messagescomprising: (i) a first location measurement obtained by the UE, thelocation server function enabled to determine an estimate location ofthe UE based at least in part on the first location measurement; (ii) arequest received by the UE for the first location measurement; (iii)first assistance data received by the UE, the first assistance dataassisting the UE to obtain the first location measurement; or (iv) acombination thereof; and means for exchanging one or more secondsignaling messages with a location server associated with a corenetwork, the one or more second signaling message comprising a secondlocation measurement obtained by the UE, a request received by the UEfor the second location measurement, second assistance data received bythe UE, the second assistance data assisting the UE to obtain the secondlocation measurement, or a combination thereof.

Another particular implementation is directed to a method of locating auser equipment (UE) at a location server associated with a core network,comprising: exchanging one or more first signaling messages with the UE,the one or more first signaling messages comprising a locationmeasurement received obtained by the UE, a request sent to the UE forthe location measurement, assistance data sent to the UE, the assistancedata assisting the UE to obtain the location measurement, or acombination thereof; and exchanging one or more second signalingmessages with a location server function associated with a radio accessnetwork, one or more second signaling message comprising locationinformation for the UE, a request for the location information for theUE, a location configuration for the UE, a request for the locationconfiguration for the UE, a location context for the UE, a request forthe location context for the UE, or a combination thereof.

Another particular implementation is directed to a location serverassociated with a core network for locating a user equipment (UE),comprising: a communication interface; and one or more processors to:exchange one or more first signaling messages through the communicationinterface with the UE, the one or more first signaling messagescomprising a location measurement received obtained by the UE, a requestsent to the UE for the location measurement, assistance data sent to theUE, the assistance data assisting the UE to obtain the locationmeasurement, or a combination thereof; and exchange one or more secondsignaling messages through the communication interface with a locationserver function associated with a radio access network, one or moresecond signaling message comprising location information for the UE, arequest for the location information for the UE, a locationconfiguration for the UE, a request for the location configuration forthe UE, a location context for the UE, a request for the locationcontext for the UE, or a combination thereof.

Another particular implementation is directed to a non-transitorystorage medium comprising computer-readable instructions stored thereonwhich are executable by one or more processors of a location serverassociated with a core network for locating a user equipment (UE) to:exchange one or more first signaling messages with the UE, the one ormore first signaling messages comprising a location measurement receivedobtained by the UE, a request sent to the UE for the locationmeasurement, assistance data sent to the UE, the assistance dataassisting the UE to obtain the location measurement, or a combinationthereof; and exchange a plurality of one or more second signalingmessages with a location server function associated with a radio accessnetwork, one or more second signaling message comprising locationinformation for the UE, a request for the location information for theUE, a location configuration for the UE, a request for the locationconfiguration for the UE, a location context for the UE, a request forthe location context for the UE, or a combination thereof.

Another particular implementation is directed to a location serverassociated with a core network for locating a user equipment (UE),comprising: means for exchanging a one or more first signaling messageswith the UE, the one or more first signaling messages comprising alocation measurement received obtained by the UE, a request sent to theUE for the location measurement, assistance data sent to the UE, theassistance data assisting the UE to obtain the location measurement, ora combination thereof; and means for exchanging a plurality of one ormore second signaling messages with a location server functionassociated with a radio access network, one or more second signalingmessage comprising location information for the UE, a request for thelocation information for the UE, a location configuration for the UE, arequest for the location configuration for the UE, a location contextfor the UE, a request for the location context for the UE, or acombination thereof.

It should be understood that the aforementioned implementations aremerely example implementations, and that claimed subject matter is notnecessarily limited to any particular aspect of these exampleimplementations.

BRIEF DESCRIPTION OF THE FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, both asto organization and/or method of operation, together with objects,features, and/or advantages thereof, it may best be understood byreference to the following detailed description if read with theaccompanying drawings in which:

FIG. 1 is a system diagram illustrating certain features of a systemcomprising a mobile device and a 4G network, in accordance with anexample implementation;

FIG. 2 is a system diagram illustrating certain features of a systemcomprising a mobile device and a 5G network, in accordance with anexample implementation;

FIG. 3 is a message flow diagram in accordance with certain exampleimplementations;

FIGS. 4-6 are flow diagrams for processes for providing positioningservices according to various embodiments;

FIG. 7 is a schematic block diagram depicting an example wirelesscommunication system including a plurality of computing platformscomprising one or more wirelessly connected devices, in accordance withan implementation;

FIG. 8 is a schematic block diagram of a mobile device, in accordancewith an example implementation; and

FIG. 9 is a schematic block diagram of an example computing platform inaccordance with an implementation.

Reference is made in the following detailed description to accompanyingdrawings, which form a part hereof, wherein like numerals may designatelike parts throughout that are identical, similar and/or analogous. Itwill be appreciated that the figures have not necessarily been drawn toscale, such as for simplicity and/or clarity of illustration. Forexample, dimensions of some aspects may be exaggerated relative toothers. Further, it is to be understood that other embodiments may beutilized. Furthermore, structural and/or other changes may be madewithout departing from claimed subject matter. References throughoutthis specification to “claimed subject matter” refer to subject matterintended to be covered by one or more claims, or any portion thereof,and are not necessarily intended to refer to a complete claim set, to aparticular combination of claim sets (e.g., method claims, apparatusclaims, etc.), or to a particular claim. It should also be noted thatdirections and/or references, for example, such as up, down, top,bottom, and so on, may be used to facilitate discussion of drawings andare not intended to restrict application of claimed subject matter.Therefore, the following detailed description is not to be taken tolimit claimed subject matter and/or equivalents.

DETAILED DESCRIPTION

References throughout this specification to one implementation, animplementation, one embodiment, an embodiment, and/or the like mean thata particular feature, structure, characteristic, and/or the likedescribed in relation to a particular implementation and/or embodimentis included in at least one implementation and/or embodiment of claimedsubject matter. Thus, appearances of such phrases, for example, invarious places throughout this specification are not necessarilyintended to refer to the same implementation and/or embodiment or to anyone particular implementation and/or embodiment. Furthermore, it is tobe understood that particular features, structures, characteristics,and/or the like described are capable of being combined in various waysin one or more implementations and/or embodiments and, therefore, arewithin intended claim scope. However, these and other issues have apotential to vary in a particular context of usage. In other words,throughout the disclosure, particular context of description and/orusage provides helpful guidance regarding reasonable inferences to bedrawn; however, likewise, “in this context” in general without furtherqualification refers to the context of the present disclosure.

A mobile device may be referred to as a device, user equipment (UE),wireless device, mobile terminal, wireless terminal, terminal, mobilestation (MS), Secure User Plane Location (SUPL) Enabled Terminal (SET)or by some other name. A mobile device (referred to synonymously hereinas a UE) may be, or may be part of, a cellphone, smartphone, tablet,laptop, wearable, tracking device, in vehicle communication system(IVS), Drone, Robot, Internet of Things (IoT) device or any othermovable entity for which wireless communication is needed or usable. Anestimated location of a mobile device may be useful or essential forcertain applications such as emergency calls, navigation, tracking,direction finding, Internet services, autonomous movement (e.g. by avehicle, drone or robot), augmented reality, virtual reality.

A location of a mobile device may be defined in geodetic terms (e.g.using X, Y and possibly Z Cartesian coordinates or using latitude,longitude and possibly altitude) and/or in civic terms (e.g. via apostal address, street address, well known landmark, building relateddesignation). A location may further be expressed in absolute terms(e.g. using latitude and longitude) or relative (e.g. by providing adistance and bearing to another defined location). A location may alsoinclude an orientation of the mobile device and may also be accompaniedby (or sometimes replaced by) a velocity (e.g. speed and direction) ofthe mobile device. An estimated location may be accompanied by a levelof certainty or uncertainty for the location—e.g. by providing an areaor volume within which the mobile is expected to be located with acertain confidence (e.g., 67%) and/or by providing an expected ormaximum error for the estimated location (e.g. such as indicating amaximum error of 100 meters with a 67% confidence level for a location).

A “location” may also be referred to herein as a location estimate,position, position estimate, position fix, location fix, fix or by someother name. A location may be highly accurate (e.g., with an error lessthan 1.0 meter) which may be needed or useful for location of a mobiledevice indoors or when associated with or part of a vehicle, drone orrobot. A location may also be less accurate (e.g., with an error of 200to 1000 meters) which may be adequate to determine in which city or townand/or in which part of a city or town a mobile device is located, whichmay suffice for some Internet services and for coarse tracking.

The term “downlink” as used herein refers to a direction of transferfrom a network, fixed transmitter or other component of aninfrastructure (e.g. satellite system) to a mobile device. Thus, forexample, a downlink signal is transmitted from a network, fixedtransmitter or satellite to a mobile device. The term “uplink” as usedherein refers to a direction of transfer from a mobile device to anetwork, fixed receiver, transceiver or other component of aninfrastructure (e.g. satellite system). Thus, for example, an uplinksignal is transmitted from a mobile device to a network, fixedtransceiver or a satellite. The term “sidelink” as used herein refers toa direction of transfer from a mobile device to another mobile device orto some other peer entity (e.g. a wearable or WPAN controller). Thus,for example, a sidelink signal is transmitted from a mobile device toanother mobile device or peer entity like a wearable or WPAN controller.The terms downlink, uplink and sidelink can also be used to distinguishdifferent types of positioning operations and methods to locate a mobiledevice as described later herein.

Techniques for positioning operations have included use of downlinkpositioning methods in which a mobile device acquires and measuresdownlink signals transmitted from some fixed or mobile entity associatedwith a network or a positioning system. One class of downlinkpositioning makes use of a satellite positioning system (SPS). Examplesof an SPS include GPS and other like global navigation satellite systems(GNSSs) such as GLONASS, Galileo and Beidou. Here, a receiver mayestimate its location at a point on (or above or possibly below) theEarth based, at least in part, on acquisition and measurement of signalstransmitted from multiple satellite-based transmitters in a GNSSconstellation. In certain conditions or implementations, positioningoperations based on acquisition and measurement of signals from GNSStransmitters may not be feasible such as in urban or indoor environmentsor for mobile devices that do not have receivers capable of acquiringand measuring signals transmitted from GNSS transmitters. GPS and GNSSbased location may be highly accurate when used outdoors (e.g. with anaccuracy as good as 10 meters) and may be able to attain sub-meteraccuracy when used in carrier-phase mode—e.g. with real time kinematics(RTK).

In certain scenarios, a cellular carrier may enable downlink positioningat a mobile device based on acquisition and measurement of signalstransmitted by a terrestrial transmitter (e.g., at a cellular basestation or WiFi access point). For example, a carrier may enablepositioning operations based on acquisition and measurement of signalstransmitted by a terrestrial transmitter using techniques such asadvanced forward trilateration (AFLT), observed time difference ofarrival (OTDOA) and enhanced cell ID (ECID). Here, signals transmittedby terrestrial transmitters and acquired and measured by a mobile devicefor use in positioning operations may comprise terrestrial positioningsignals. In this context, a “terrestrial positioning signal” (TPS)comprises a signal that may be acquired by a mobile device and that hasone or more characteristics that may be measured by the mobile device. ATPS may correspond to the physical layer of a radio interface (e.g.“layer 1” or “level 1”) and may comprise a particular component,portion, subset, signal and/or set of signals transmitted as part of thephysical layer. The acquisition and measurement by the mobile device ofa TPS may involve coherent or non-coherent integration of the TPS overtime (e.g. over a period of 20 ms to 100 ms)—e.g. in the case that a TPShas a signal strength below the noise floor. Characteristics of a TPSthat may be measured may include a received signal strength indication(RSSI), a time of arrival (TOA), a signal to noise ratio (S/N), an angleof arrival (AOA), a round trip signal propagation time (RTT), areference signal received power (RSRP), a reference signal receivedquality (RSRQ), and a reference signal time difference (RSTD).

The term “positioning reference signal” (PRS), as used herein, denotes aterrestrial signal that has been defined and/or implemented specificallyto support positioning. The term “terrestrial positioning signal” (TPS),as used herein, includes any terrestrial signal that can be measured tosupport location of a mobile device. A TPS may be used for otherpurposes—e.g. to assist network access by a mobile device, assistnetwork operation, convey control information, convey voice or data. ATPS may be (though need not be) a PRS. A PRS, by contrast, is always aTPS. To assist readability, a TPS and a PRS are sometimes referred toherein as a “TPS signal” and a “PRS signal”, respectively, even though,strictly speaking, the word “signal” in such a usage is redundant.

According to specifications from the 3^(rd) Generation PartnershipProject (3GPP), networks supporting 4G Long Term Evolution (LTE) mayemploy a TPS that comprises a PRS, defined according to 3GPP technicalspecification (TS) 36.211, for use in OTDOA. A PRS used to assist OTDOAin the case of LTE access may also be highly accurate when transmitters(e.g. base stations) are precisely time synchronized (e.g. GPSsynchronized) and may achieve an accuracy of 10-50 meters in bothoutdoor and indoor environments. A TPS or PRS signaling may sometimes bereferred to as being transmitted at a level 1, a layer 1 (e.g. a 5Glayer 1) or at a physical level or in a physical layer because a TPS orPRS signal is typically defined (e.g. in the case of 3GPP) as part ofthe physical level or bottom most (layer 1) of a radio interface.

A TPS may be transmitted by a transmission point (TP) which may be aterrestrial transmitter such a base station (BS), evolved NodeB (eNodeBor eNB), a TP for a terrestrial beacon system (TBS), an access point(AP) or other transmitter. The term transmission point (TP), as usedherein, represents any kind of terrestrial transmitter that may be usedfor downlink positioning including a cellular base station (BS), a homeBS, a femtocell and a WiFi access point (AP). The term transmissionbeacon (TB), as used herein, refers to any terrestrial transmitter thattransmits a TPS but is not used to support uplink communication frommobile devices. A TP may thus be a transceiver (e.g. a cellular basestation) or may be a TB capable only of transmitting. The class of TBsis thus a subset of the class of TPs. The term base station (BS) is alsoused herein in a generic sense to refer to a cellular base station, asmall cell, an access point, femtocell or picocell that supportswireless access from one or more devices involving two way radiotransmission which may be full duplex though may also be half duplex.

In a particular implementation, a TPS may occupy a dedicated portion ofthe spectrum of a downlink signal transmitted by a TP. The dedicatedportion of spectrum used by a TPS may comprise a particular frequency orfrequencies, a particular bandwidth and/or particular transmission times(e.g., timeslots, frames or subframes) which may be fixed or may varyover time (e.g., via frequency hopping and/or via periodic reschedulingof transmission times). A TP (e.g., by transmitting broadcastinformation) or a server on the network side (e.g., by sendingassistance data) may provide a mobile device with characteristics of aPRS or TPS including the dedicated portion of spectrum being used (e.g.,frequency or frequencies, bandwidth and/or transmission times), the TPSsignal coding, approximate expected TOA or RSTD at the mobile device forthe TPS and/or any muting of the TPS in order to assist the mobiledevice to accurately, reliably and efficiently acquire and measure thePRS or TPS. In the case of a future 5G radio interface, TPS and/or PRSsignals may be defined and used to support measurements of RSSI, S/N,RTT, AOA, RSRP, RSRQ, RSTD and/or other signal characteristics for the5G radio interface, which may be used to determine or help determine thelocation of a mobile device.

Positioning of a UE may also be supported using sensors attached to,embedded within or otherwise accessible from a UE including inertialsensors and/or other environmental sensors. Inertial sensors may includean accelerometer, magnetometer, gyroscope and/or compass. Environmentalsensors may include a thermometer, barometer, microphone, camera and/orhygrometer. Inertial sensors may be able to detect and measure changesin motion of a UE (e.g. a change of speed and/or direction), whileenvironmental sensors may be able to measure altitude (e.g. viabarometric pressure) and/or characteristics of a local environment thatmay help determine a UE location. A UE may provide measurements obtainedfrom sensors and/or location related information obtained from suchmeasurements (e.g. a current altitude, current speed or recent change inlocation) to a location server to assist the location server indetermining a current UE location. A location server may also provideassistance data to a UE to help calibrate or make use of somesensors—such as providing a known atmospheric pressure at some knownreference location nearby to a UE to assist the UE in determining acurrent altitude from a measured atmospheric pressure at the currentlocation of the UE.

Positioning of a UE can be supported by a number of uplink terrestrialposition methods, also referred to as “network based” position methods,in which a base station (e.g., eNodeB), access point (AP) (e.g., IEEE802.11 AP) or a location measurement unit (LMU) acquires and measures anuplink signal (e.g., TPS) transmitted by a UE. The uplink signal mayhave properties similar to or the same as a downlink TPS or PRS or maysimply be any signal transmitted by a UE for other purposes such assending control information, voice or data to a network (or possiblysome remote entity). Characteristics of an uplink signal that may bemeasured can be similar to or the same as characteristics of a downlinksignal and may include RSSI, S/N, TOA, RTT, RSRP, RSRQ, AOA. Uplinkposition methods may include measurements of uplink time difference ofarrival (UTDOA), which may be based on measuring TOA and enhanced cellID (ECID). Measurements of TOA and ECID may be further based onmeasuring other characteristics such as RSSI, RTT, S/N, RSRP, RSRQ andAOA.

In other embodiments, a UE may determine or obtain measurements toestimate a location of the UE based, at least in part, on signalstransmitted between the UE and other peer device such as other UEs.Position methods based on signals transmitted between a UE and a peerdevice may be referred to as sidelink position methods and the measuredsignals as sidelink signals. For example, measurements of signalstrength and/or round-trip time of signals transmitted between or amongpeer UE devices may be used for computation of a range (e.g., straightline distance) between or among the UE devices. Such measurements ofrange between or among peer UE devices may be used to estimate, or helpestimate, a relative or absolute location of at least one of the UEdevices. Signals that are exchanged between or among UEs and other peerdevices, and measured to support or help support UE location may includesignals transmitted according to Bluetooth®, Bluetooth Low Energy(BTLE), IEEE 802.11 WiFi, LTE Direct (LTE-D), WiFi Direct (WiFi-D), LTEunlicensed (LTE-U) and/or one or more future 5G radio interfaces, justto provide a few examples.

To support positioning of a mobile device, two broad classes of locationsolution have been defined: control plane and user plane. With controlplane (CP) location, signaling related to positioning and support ofpositioning may be carried over existing network (and mobile device)interfaces and using existing protocols dedicated to the transfer ofsignaling. With user plane (UP) location, signaling related topositioning and support of positioning may be carried as part of otherdata using such protocols as the Internet Protocol (IP), TransmissionControl Protocol (TCP) and User Datagram Protocol (UDP). Control planesolutions can support all three types of positioning referred topreviously as downlink, uplink and sidelink positioning. User planesolutions may support only downlink position methods, though uplink andsidelink position methods may be supported with some extensions—e.g. bytreating one UE as a location server in the case of user plane locationbetween a pair of UEs.

3GPP has defined control plane location solutions for mobile devicesthat use radio access according to Global System for Mobilecommunications GSM (2G), Universal Mobile Telecommunications System(UMTS) (3G) and LTE (4G). A control plane solution for future 5G accessmay be defined in future. These solutions are defined in 3GPP TSs 23.271(common part), 43.059 (GSM access), 25.305 (UMTS access) and 36.305 (LTEaccess). The Open Mobile Alliance (OMA) has similarly defined a UPlocation solution known as Secure User Plane Location (SUPL) which canbe used to locate a mobile device accessing any of a number of radiointerfaces that support IP packet access such as General Packet RadioService (GPRS) with GSM, GPRS with UMTS, or IP access with LTE.

Both CP and UP location solutions may employ a location server (LS) tosupport positioning. The LS may be part of or accessible from a servingnetwork or a home network for a UE or may simply be accessible over theInternet or over a local Intranet. If positioning of a UE is needed, anLS may instigate a session (e.g. a location session or a SUPL session)with the UE and coordinate location measurements by the UE anddetermination of an estimated location of the UE. During a locationsession, an LS may request positioning capabilities of the UE (or the UEmay provide them without a request), may provide assistance data to theUE (e.g. if requested by the UE or in the absence of a request) and mayrequest a location estimate or location measurements from a UE (e.g. forthe GNSS, OTDOA and/or ECID position methods). Assistance data may beused by a UE to acquire and measure GNSS, TPS and/or PRS signals (e.g.by providing expected characteristics of these signals such asfrequency, expected time of arrival, signal coding, signal Doppler).

In a UE based mode of operation, assistance data may also or instead beused by a UE to help determine a location estimate from the resultinglocation measurements (e.g., if the assistance data provides satelliteephemeris data in the case of GNSS positioning or TP locations and otherTP characteristics such as TPS or PRS timing in the case of terrestrialpositioning).

In an alternative UE assisted mode of operation, a UE may returnlocation measurements to an LS which may determine an estimated locationof the UE based on these measurements in addition to other known orconfigured data (e.g. satellite ephemeris data for GNSS location or TPcharacteristics including TP locations and possibly TPS/PRS timing inthe case of terrestrial positioning).

In another standalone mode of operation, a UE may make location relatedmeasurements without any assistance data from an LS and may furthercompute a location or a change in location without any assistance datafrom an LS. Position methods that may be used in a standalone modeinclude GPS and GNSS (e.g. if a UE obtains satellite orbital data fromdata broadcast by GPS and GNSS satellites themselves) as well assensors.

In the case of 3GPP CP location, an LS may be an enhanced serving mobilelocation center (E-SMLC) in the case of LTE access, a standalone SMLC(SAS) in the case of UMTS access or a serving mobile location center(SMLC) in the case of GSM access. In the case of OMA SUPL location, anLS may be a SUPL Location Platform (SLP) which may act as any of: (i) ahome SLP (H-SLP) while in or associated with the home network of a UE orwhile providing a permanent subscription to a UE for location services;(ii) a discovered SLP (D-SLP) while in or associated with some other(non-home) network or while not associated with any network; (iii) anEmergency SLP (E-SLP) while supporting location for an emergency callinstigated by the UE; or (iv) a visited SLP (V-SLP) while in orassociated with a serving network or a current local area for a UE.

An entity that is “associated with” a network, as described herein, maybe physically part of the network, directly connected to one or moreentities within the network, or may be accessible from the network andbelong to the operator or owner of the network

During a location session, an LS and UE may exchange messages definedaccording to some positioning protocol in order to coordinate thedetermination of an estimated location. Possible positioning protocolsmay include, for example, the LTE Positioning Protocol (LPP) defined by3GPP in 3GPP TS 36.355 and the LPP Extensions (LPPe) protocol defined byOMA in OMA TSs OMA-TS-LPPe-V1_0, OMA-TS-LPPe-V1_1 and OMA-TS-LPPe-V2_0.The LPP and LPPe protocols may be used in combination where an LPPmessage contains one embedded LPPe message. The combined LPP and LPPeprotocols may be referred to as LPP/LPPe. LPP and LPP/LPPe may be usedto help support the 3GPP control plane solution for LTE access, in whichcase LPP or LPP/LPPe messages are exchanged between a UE and E-SMLC. LPPor LPPa messages may be exchanged betweenm a UE and E=SMLC via a servingMobility Management Entity (MME) and a serving eNodeB for the UE. LPPand LPP/LPPe may also be used to help support the OMA SUPL solution formany types of wireless access that support IP messaging (such as LTE andWiFi) where LPP or LPP/LPPe messages are exchanged between a SET (theterm used for a UE with SUPL) and an SLP, which may be transportedwithin SUPL messages such as a SUPL POS or SUPL POS INIT message

According to an embodiment, both LPP and LPPe (and LPP/LPPe) may supportthe types of messages shown in Table 1 which may be valid for use withboth CP and UP location solutions. The different columns in Table 1 showthe message name, allowed direction of transfer for each message and apurpose of each message. In the case of LPPe, a “reversed mode” issupported that allows an LS and UE to swap their normal roles andtransfer the two Capabilities and two Location Information messages inthe opposite direction to that indicated in Table 1.

TABLE 1 Message Name Direction Purpose Request Capabilities LS to UE LSrequests UE positioning capabilities Provide Capabilities UE to LS UEprovides its positioning capabilities Request Assistance Data UE to LSUE requests assistance data for UE assisted and/or UE based locationProvide Assistance Data LS to UE LS provides assistance data for UEassisted and/or UE based location Request Location LS to UE LS requestslocation Information measurements or a location estimate from a UEProvide Location UE to LS UE provides location Information measurementsor a location estimate to an LS Error Both UE or LS indicates a protocolor procedural error Abort Both UE or LS aborts a location session

FIG. 1 exemplifies a system 100 capable of supporting location of a UE102 that has LTE access. System 100 may support both control planelocation according to the 3GPP CP location solution defined in 3GPP TSs23.271 and 36.305, and user plane location according to any of the OMASUPL solutions defined in OMA TSs OMA-TS-ULP-V2_0_3, OMA-TS-ULP-V2_1 andOMA-TS-ULP-V3_0. However, actual systems may only include support forone of these (CP or UP location), or neither. System 100 is illustrativeof features capable of supporting operations for determining locationestimates in 4G networks but not necessarily 5G networks.

According to an embodiment, system 100 may be referred to as an EvolvedPacket System (EPS). As illustrated, system 100 may include a UE 102, anEvolved UMTS Terrestrial Radio Access Network (E-UTRAN) 120, and anEvolved Packet Core (EPC) 130. The E-UTRAN 120 and the EPC 130 may bepart of a Visited Public Land Mobile Network (VPLMN) capable ofcommunicating with a Home Public Land Mobile Network (HPLMN) 140 for theUE 102. System 100 may interconnect with other networks. For example,the Internet may be used to carry messages to and from differentnetworks such as the HPLMN 140 and the VPLMN EPC 130. For simplicitythose other networks are not shown in FIG. 1. As shown, system 100 mayprovide packet-switched services, however, as those skilled in the artwill readily appreciate, the various concepts and features presentedthroughout this disclosure may be extended to networks providingcircuit-switched services.

UE 102 may comprise any electronic device configured for LTE radioaccess. UE 102 may be referred to as a mobile device or by other names,as previously discussed, and may correspond to (or be part of) a smartwatch, digital glasses, and fitness monitor, smart cars, smartappliances, cellphone, smartphone, laptop, tablet, PDA, IoT device,tracking device, control device, or some other portable or moveabledevice. The UE 102 may comprise a single entity or may comprise multipleentities such as in a personal area network where a user may employaudio, video and/or data I/O devices and/or body sensors and a separatewireline or wireless modem. Typically, though not necessarily, the UE102 may support wireless communication such as using GSM, Code DivisionMultiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate PacketData (HRPD), IEEE 802.11 WiFi, Bluetooth (BT), WiMax, etc. UE 102 mayalso support wireless communication using a wireless LAN (WLAN), DigitalSubscriber Line (DSL) or packet cable for example. Although FIG. 1 showsonly one UE 102, system 100 may include having features of UE 102 asdescribed herein.

The UE 102 may enter a connected state with a wireless communicationnetwork that may include the E-UTRAN 120. In one example, UE 102 maycommunicate with a cellular communication network by transmittingwireless signals to, or receiving wireless signals from, a cellulartransceiver, such as a serving evolved Node B (eNB) 104 in the E-UTRAN120. The E-UTRAN 120 may include one or more additional eNBs 106. TheeNB 104 may provide user and control plane protocol terminations towardthe UE 102. The eNB 104 may also be referred to as a base station, abase transceiver station, a radio base station, a radio transceiver, aradio network controller, a transceiver function, a base stationsubsystem (BSS), an extended service set (ESS), or by some othersuitable terminology. The UE 102 also may transmit wireless signals to,or receive wireless signals from, a local transceiver, such as an accesspoints (AP), femtocell, Home Base Station, small cell base station, HomeNode B (HNB) or Home eNodeB (HeNB) and may provide access to a wirelesslocal area network (WLAN, e.g., IEEE 802.11 network), a wirelesspersonal area network (WPAN, e.g., Bluetooth network) or a cellularnetwork (e.g. an LTE network or other wireless wide area network). Ofcourse it should be understood that these are merely examples ofnetworks that may communicate with a mobile device over a wireless link,and claimed subject matter is not limited in this respect.

Examples of radio access technologies that may support wirelesscommunication include Narrow Band Internet of Things (NB-IoT), GlobalSystem for Mobile Communications (GSM), Code Division Multiple Access(CDMA), Wideband CDMA (WCDMA), Long Term Evolution LTE), High RatePacket Data (HRPD). NB-IoT, GSM, WCDMA and LTE are technologies definedby 3GPP. CDMA and HRPD are technologies defined by the 3rd GenerationPartnership Project 2 (3GPP2). WCDMA is also part of the UniversalMobile Telecommunications System (UMTS) defined by 3GPP. Cellulartransceivers, such as eNBs 104, 106, may comprise deployments ofequipment providing subscriber access to a wireless telecommunicationnetwork for a service (e.g., under a service contract). Here, a cellulartransceiver may perform functions of a cellular base station inservicing subscriber devices within a cell determined based, at least inpart, on a range at which the cellular transceiver is capable ofproviding access service.

The eNBs 104, 106 are connected by an interface to the VPLMN EPC 130.EPC 130 includes a Mobility Management Entity (MME) 108, and a ServingGateway (SGW) 112, through which IP packets are transferred to and fromthe UE 102. The MME 108 may comprise a serving MME for UE 102 andprovide a control node that processes the signaling between the UE 102and the EPC 130, and supports attachment and network connection of UE102. MME 108 may also establish and release data bearers on behalf ofthe UE 102. In an implementation, MME 108 may provide bearer andconnection management for the UE 102, and may be connected to the SGW112, the eNBs 104 and 106, the E-SMLC 110 and a Visited Gateway MobileLocation Center (V-GMLC) 116 in the VPLMN EPC 130.

E-SMLC 110 may support determining an estimated location of the UE 102using the 3GPP control plane (CP) location solution as previouslydescribed. V-GMLC 116, which may also be referred to simply as a GatewayMobile Location Center (GMLC) 116, may provide access on behalf of anexternal client (e.g. external client 150) or another network (e.g.HPLMN 140) to the location of UE 102.

As illustrated, HPLMN 140 may include (i) a Home Gateway Mobile LocationCenter (H-GMLC) 148 that may be connected to the V-GMLC 116 (e.g. viathe Internet), and (ii) a Packet Data Network Gateway (PDG) 114 that maybe connected to the SGW 112 (e.g. via the Internet). PDG 114 may provideUE 102 with IP address allocation and IP and other data access toexternal networks (e.g., the Internet), external clients (e.g. externalclient 150) and external servers, as well as other data transfer relatedfunctions. In some implementations, PDG 114 may be located in VPLMN EPC130 and not in HPLMN 140 when the UE 102 receives local IP breakout. MME108 and PDG 114 may be connected to location servers, such as E-SMLC 110and H-SLP 118, respectively. H-SLP 118 may support the SUPL UP locationsolution as previously described and may comprise an H-SLP for UE 102.In the case that PDG 114 is located in VPLMN EPC 130 with local IPbreakout, H-SLP 118 may be replaced by a D-SLP or E-SLP that isconnected to PDG 114. H-GMLC 148 may be connected to the Home SubscriberServer (HSS) 145, which may comprise a central database containinguser-related and subscription-related information for UE 102. H-GMLC 148may provide location access to the UE 102 for external clients such asexternal client 150. One or more of the H-GMLC 148, PDG 114, and H-SLP118 may be connected to the external client 150, e.g., through anothernetwork, such as the Internet.

In some cases, a Requesting GMLC (R-GMLC) located in another PLMN (notshown in FIG. 1) may be connected to H-GMLC 148 (e.g. via the Internet)in order to provide location access to UE 102 on behalf of externalclients connected to the R-GMLC. The R-GMLC, H-GMLC 148 and V-GMLC 116may support location access to the UE 102 using the 3GPP CP locationsolution for LTE access that was mentioned previously.

It should be understood that while a VPLMN network (comprising VPLMNE-UTRAN 120 and VPLMN EPC 130) and a separate HPLMN 140 are illustratedin FIG. 1, both PLMNs (networks) may comprise the same PLMN. This mayoccur while the UE 102 receives wireless access from its home PLMN andis not roaming in some other VPLMN. In that case, (i) H-SLP 118, PDG114, and HSS 145, may be in the same network (EPC) as the MME 108,E-SMLC 110 and SGW 112, and (ii) the V-GMLC 116 and the H-GMLC 148 maycomprise the same GMLC.

In particular implementations, UE 102 may have circuitry and processingresources capable of supporting downlink positioning, uplinkpositioning, sidelink positioning and/or location using sensors aspreviously described. In addition, in the case of downlink positioning,UE 102 may support one or more position methods that may be used in UEassisted, UE based and/or standalone modes. UE 102 may be furthercapable of supporting location estimation according to the 3GPP CPlocation solution for LTE access and/or the SUPL UP location solution.Furthermore, UE 102 may support the LPP, LPPe and/or combined LPP/LPPepositioning protocols.

As non-limiting examples of positioning support, UE 102 may supportlocation related measurements using downlink signals from GPS or otherGNSS satellite vehicles (SVs) 160 and/or downlink signals from cellulartransceivers such as eNBs 104, 106, and may support computing anestimated location of UE 102 based on these location relatedmeasurements (e.g., for UE based mode). In some implementations,location related measurements obtained by UE 102 may be transferred toan LS, such as E-SMLC 110 or H-SLP 118, for UE assisted mode after whichthe LS may estimate a location for UE 102 based on the location relatedmeasurements.

Location related measurements obtained by UE 102 may include pseudorangemeasurements of signals received from SVs 160. The pseudorangemeasurements may comprise measurements of the code phase of a navigationsignal transmitted by an SV 160. In addition or as an alternative, UE102 may measure a carrier phase for a navigation signal transmitted byan SV 160 which may enable very precise location (e.g. centimeter levelaccuracy) using RTK. UE 102 may also or instead obtain measurements ofRSSI, RTT, S/N, RSRP, RSRQ, AOA and/or RSTD for TPS signals receivedfrom eNBs 104 and 106 and/or other base stations and APs not shown inFIG. 1. UE 102 or the LS (e.g. E-SMLC 110 or H-SLP 118) may then obtaina location estimate for UE 102 based on these location relatedmeasurements using any one of several position methods such as, forexample, GNSS, Assisted GNSS (A-GNSS), RTK, AFLT, OTDOA, E-CID orcombinations thereof. In some of these techniques (e.g. A-GNSS, AFLT andOTDOA), pseudoranges or timing differences (e.g. RSTDs) may be measuredby UE 102 relative to three or more terrestrial TPs fixed at knownlocations or relative to four or more satellites with accurately knownorbital data, or combinations thereof, based at least in part, onpilots, TPS signals, PRS signals (or other positioning related signals)transmitted by the TPs or satellites and received at the UE 102. Here,location servers, such as E-SMLC 110 or H-SLP 118, may be capable ofproviding positioning assistance data to UE 102 including, for example,information regarding signals to be measured (e.g., expected signaltiming, signal coding, signal frequencies, signal Doppler), locationsand identities of terrestrial TPs and/or signal, timing and orbitalinformation for GNSS satellites to facilitate positioning techniquessuch as A-GNSS, AFLT, OTDOA and E-CID. Such facilitation of positioningtechniques such as A-GNSS, AFLT, OTDOA and E-CID may include improvingsignal acquisition and measurement accuracy by UE 102 and, in somecases, enabling UE 102 to compute its estimated location based on thelocation measurements. For example, location servers may comprise analmanac which indicates locations and identities of cellulartransceivers (e.g. eNBs 104 and 106) and/or local transceivers in aparticular region or regions such as a particular venue, and may provideinformation descriptive of signals transmitted by a cellular basestation or AP such as transmission power and signal timing.

In order to coordinate location of UE 102 using the 3GPP control planelocation solution with downlink positioning, UE 102 and E-SMLC 110 mayexchange LPP or LPP/LPPe messages 160. LPP or LPP/LPPe messages 160 maybe transferred between UE 102 and E-SMLC 110 via serving eNB 104 andserving MME 108. LPP or LPP/LPPe messages may include the types ofmessages shown in Table 1. For example, an LPP or LPP/LPPe ProvideLocation message may be used by UE 102 to send downlink location relatedmeasurements to E-SMLC 110.

In order to coordinate location of UE 102 using the 3GPP control planelocation solution with uplink positioning, E-SMLC 110 may exchange LPPaannex (LPPa) messages 162 with serving eNB 104. LPPa and LPPa messages162 may be defined according to 3GPP TS 36.455. LPPa messages 162 may betransferred between eNB 104 and E-SMLC 110 via serving MME 108. Forexample, E-SMLC 110 may send an LPPa message to eNB 104 to requestuplink location measurements by eNB 104 of TPS signals transmitted by UE102, such as measurements of RSSI, RSRP, RSRQ, AOA, S/N, and AOA. eNB104 may then obtain and returned the requested measurements to E-SMLC110 by sending another LPPa message to E-SMLC 110 via serving MME 108.E-SMLC 110 may also send an LPPa message to serving eNB 104 to requestcurrent configuration information for eNB 104 such as the preciselocation of an antenna for eNB 104 and/or timing information for TPSsignals transmitted by eNB 104. In the case that eNB 104 manages morethan one cell (e.g. manages a number of cell sectors, remote radio heads(RRHs) and/or remote TBs), E-SMLC may request configuration information(e.g. antenna location and TPS timing) for each cell, each RRH and/oreach remote TB that eNB 104 manages. eNB 104 may then return therequested information in one or more LPPa messages back to E-SMLC 110.

In order to coordinate location of UE 102 using the OMA SUPL UP locationsolution, UE 102 and H-SLP 118 may exchange SUPL UserPlane LocationProtocol (ULP) messages 164 as defined in OMA-TS-ULP-V2_0_3,OMA-TS-ULP-V2_1 or OMA-TS-ULP-V3_0. One or more of the exchanged SUPLULP messages 164 may further include one or more embedded LPP orLPP/LPPe messages. SUPL ULP messages 164 may be transferred between UE102 and H-SLP 118 using UDP/IP or TCP/IP via serving eNB 104, SGW 112and PDG 114. LPP or LPP/LPPe messages that are embedded in SUPL ULPmessages 164 may include the types of messages shown in Table 1. Forexample, an LPP or LPP/LPPe Provide Location message (embedded in one ofthe SUPL ULP messages 164) may be used by UE 102 to send downlinklocation related measurements to H-SLP 118.

FIG. 1 is illustrative of location support in a 4G wireless system suchas an LTE network (also known as an EPS). To support estimating alocation of a UE 102 in a 5G wireless system, it may be desirable tosupport some or all of the location features for a 4G system and someadditional features that may not be supported in a 4G system. Table 2shows a set of possible location features that may be applicable to a 5Gsystem for a number of different categories of features.

TABLE 2 Feature Category Location Features applicable to 5G Positioningservices Positioning may be available to all services, clients andapplications. Positioning Methods Positioning methods may use downlink,uplink and/or sidelink signals. TPS and PRS TPS and PRS signals may beoptimized for positioning measurements (e.g. RSSI, RSTD, AGA, TOA, RTTetc.). Interference to TPS signals from other TPS signals and/or fromother non-TPS signals may be reduced via (i) periodic muting ofpotentially interfering signals; (ii) separation of TPS signals fromother TPS signals and/or from other signals in the frequency, code, timeand/or spatial domains; and/or (iii) interference cancellationtechniques. TPs TPs may be synchronized to some common time (e.g. GPStime) or unsynchronized. Broadcast Assistance data may be provided toUEs via broadcast from TPs as well as (or instead of) from an LS.Broadcast of assistance data to UEs may be unciphered and available toall UEs and/or may be ciphered and available only to authenticated andsubscribed UEs.

To support positioning in a 5G system using radio signals defined for5G, the same or similar TPS signals could in principle be used as in 4Gsystems. Since the 5G radio interface, referred to as the “New Radio”(NR) in the case of 3GPP, may differ (possibly significantly) from LTEas used for 4G in order to achieve higher data and signaling rates,greater spectrum efficiency, higher capacity and lower latency, TPSsignals in 5G may differ also from TPS signals for 4G. Table 3 shows anumber of possible characteristics for a 5G TPS (or for different 5GTPSs) and for their associated TPs that may be desirable for a 5G systemto improve location estimation support (e.g. enable more accurate andreliable location estimation, lower latency, higher capacity, greaterefficiency and/or reduced complexity and cost).

TABLE 3 Characteristic Description Scheduling Downlink and possiblyuplink TPS signals may be scheduled to reduce bandwidth usage such thata TPS signal is transmitted at only certain times that may be made knownin advance to a UE in the case of downlink signals (e.g. via assistancedata from an LS or assistance broadcast from a TP). The scheduling of adownlink TPS may be varied such that a TPS is only transmitted while UEsin the coverage area of the TPS need to or may need to measure the TPS.Scheduling of a TPS may reduce bandwidth usage by avoiding transmissionof a TPS at times when it need not be measured. Spatial A downlink TPSmay be spatially confined via Confinement transmission in certain cellsand/or via directional transmission (e.g. using an antenna array).Spatial confinement of a TPS may be used to send a TPS to UEs attemptingto measure the TPS and avoid sending the TPS to areas where UEs are notattempting to measure the TPS, which may improve bandwidth usage andreduce interference with respect to the areas to which a TPS is nottransmitted. TPS IDs A TPS (e.g. a PRS) may be encoded using a sequenceof symbols that may be defined by one or more parameters such as one ormore integers. These parameters may help identify the TPS since they maydefine its code sequence and may thus be regarded as TPS identifiers(IDs). For example, in the case of a PRS for LTE defined in 3GPP TS36.211, the PRS code sequence may be defined by a single integer between0 and 504 or between 0 and 4095 which provide a non- unique PRS ID. A UEmay store the IDs and other information associated with a downlink TPS(e.g. an inferred location or an inferred ID for the source TP of adownlink TPS) and use this later to assist location of the UE. A UE mayalso crowdsource the same TPS information to a server for later downloadto other UEs to assist location of these UEs when able to receive andmeasure the same TPS. An operator preferring not to allow use of theirTPS signals to assist location of non-authorized UEs may periodicallychange the TPS ID(s) - e.g. randomly - to attempt to make informationstored or crowdsourced by UEs not remain valid for very long. This maybe used, for example, for TPS signals transmitted by base stations,remote radio heads and by TBs. Frequencies TPS signals could use severaldifferent frequency bands including licensed and unlicensed bands.Antenna Arrays A TPS signal may be transmitted in a particular directionor certain set of directions using an antenna array - e.g. an antennaarray for multiple-input and multiple-output (MIMO) radio operation.This may improve signal acquisition and measurement accuracy and mayenable more accurate measurement of an AOA or angle of departure (AOD).A TP may also rotate a downlink TPS (e.g. over 360 degrees for acircular rotation or a smaller angle for rotation within an arc) viaelectronic means using an antenna array, which may enable a UE or an LSto determine the direction of the TPS while measured by a UE, which maythen be used to infer an AOA or AOD and thence assist location of theUE. TBs Transmission beacons (TBs) may be used to increase the number ofTPs visible to a UE whose TPS signals can be measured. This may assistlocation in areas where not many TPs are otherwise visible (e.g. insidea building or in a dense urban area). Because TBs may only need totransmit a TPS and may not need to support wireless communications (e.g.may not need to function as a BS or AP), the cost of deploying TBs maybe significantly less than the cost of deploying other types of TP whichmay enable an operator to improve accurate location support for servedUEs in a cost effective manner. TP Positioning A TP or TB may bepositioned using other TPs and/or TBs if the TP or TB to be positionedmeasures TPS signals transmitted by these other TPs and/or TBs, and/orif the other TPs and/or TBs measure TPS signals transmitted by the TP orTB to be positioned. The same or similar position methods may be used asare used to locate a UE (e.g. OTDOA, ECID, UTDOA). Locations of some TPsor TBs may be used initially (e.g. as obtained using surveying or GPS),but the locations of other TPs and TBs may be obtained from theseinitial locations using measurements of TPS signals.

In addition to improvements in physical layer support for a new 5Gsystem using measurements of TPS signals transmitted by TPs, locationsupport may be improved at higher layers and in association with aspectsof a 5G system other than TPS signals and associated TPs. Possiblehigher layer features that could improve location support for a 5Gsystem are described in Table 4.

TABLE 4 Feature Description Unauthenticated Location estimation ofunauthenticated UEs is not UEs normally supported in 2G, 3G and 4Gsystems except for unauthenticated UEs that instigate an emergency call.A 5G system might provide some limited or extended support of locationfor unauthenticated UEs as a free service associated with a network. Forexample, a network associated with a venue (e.g. shopping mall, airportconvention center, sports arena, college campus) may provide locationsupport to all UEs (authenticated and unauthenticated) as a means ofimproving overall service to users within the venue. Multi Tier Locationsupport in a 5G network may be tiered into Architecture two or moredifferent domains. As an example, a 3- tier architecture could comprisea Radio Access Network (RAN) domain, Core Network (CN) domain and aDevice to Device (D2D) domain. The D2D domain may be limited to UEpositioning using sidelink TPS signals and may also be referred to as aUE domain. The RAN domain may be limited to use of 5G TPS signals forpositioning and possibly other (e.g. GNSS) signals and may involve UEsand RAN elements only (e.g. UEs, BSs and APs). The CN domain mayfunction in a similar manner to location support using an LS for a 4Gsystem, as described for FIG. 1, and may support multiple RANs (e.g. 3GRAN, 4G RAN, 5G RAN and/or other radio access types such as WiFi), makeuse of one or more LSs in or associated with a CN and may supportcontrol plane and/or user plane location solutions. Architecture The UE,RAN and CN domains may support one Domains another or operateindependently and/or autonomously (e.g. when a domain is absent). As anexample, some 5G networks could support the RAN domain but not the CNdomain and vice versa. Positioning Usage Location results for UEs (e.g.obtained by a RAN domain or a CN domain) may be used for real timenetwork optimization and to support UE cell selection and handover.Location Services The CN and/or RAN domains may support improved triggerbased location of UEs - e.g. periodic location or triggered locationbased on UE movement, UE cell change, or environment change for a UE.

FIG. 2 exemplifies a system 200 capable of supporting estimation of alocation of a UE 102 that has wireless access according to a fifthgeneration (5G) radio access interface such as a 3GPP 5G new radio (NR)interface. System 200 may also be applicable to a UE 102 that has othertypes of radio access such as LTE, IEEE 802.11 WiFi, UMTS, GSM, BT etc.System 200, including one or more of 5G BS 220, 5G BS 222, 5G TB 224,LSF 232 and location server (LS) 226, may support some or all of thelocation estimation features, characteristics and high level featuresdescribed previously in Tables 2, 3 and 4. For ease of interpretation ofFIG. 2, unidirectional or bidirectional control signaling between pairsof entities belonging to a CN domain is shown using solid lines;unidirectional or bidirectional control signaling between pairs ofentities belonging to a RAN domain or a D2D domain is shown using boldsolid lines and bold dashed lines; and transfer of radio frequency (RF)TPS and PRS signals is shown using arrows where an arrow directionindicates a possible transmission direction of a TPS or PRS signal. Forall signaling transmitted to the UE 102 from a RAN domain, transmissionusing point to point means or using broadcast is allowed.

The terms “control signaling”, “signaling messages” and “controlsignaling messages” are used synonymously herein to refer to messages,parts of a message (e.g. one or parameters) or other signalinginformation (e.g. a sequence of bits or symbols) that are transmittedfrom one entity to one or more other entities to coordinate, manageand/or assist procedures and techniques used for network operation andUE support, such as support of location estimation related services fora UE 102. Control signaling may be transferred using wireline, wirelessor both wireline and wireless means and/or using point to point,multicast or broadcast means. One or more protocols may be used totransport control signaling (or signaling messages) such as the InternetProtocol (IP), Transmission Control Protocol (TCP), User Data Protocol(UDP) or Stream Control Transmission Protocol (SCTP). Furthermore, oneor more application level protocols may define the information contentof control signaling, such as the OMA ULP, OMA LPPe, OMA Mobile LocationProtocol (MLP), 3GPP LPP and 3GPP LPPa protocols in the case of locationservices. Control signaling may be transmitted directly between twoentities when the entities are directly connected to one another (e.g.as in the case of control signaling sent from 5G BS 220 to either 5G BS222 or UE 102) or may be sent via one or more intermediate entities(e.g., as in the case of control signaling transmitted from a standaloneLSF 232 to UE 102 via 5G BS 222, or control signaling 246 sent from LS226 to UE 102 via 5G BS 222). Control signaling that is sent betweenelements in a RAN or between an element in a RAN and a UE may bereferred to as level 3 signaling or occurring at a layer 3 (or 5G layer3) because the protocols used in 3GPP to support such signaling (e.g. aRadio Resource Control (RRC) protocol) typically occur at a layer 3 in aso called seven layer ISO/SNA model.

While control signaling is sent via one or more intermediate entities,signaling content that is defined by an application level protocol (e.g.ULP, LPP, LPPe) may not be changed, but signaling content that isassociated with a transport protocol (e.g. IP, TCP, UDP, SCTP) may bechanged if the transport protocols used along the path of the controlsignaling change due to protocol conversion at an intermediate entity.For example, if LS 226 sends an LPP signaling message to UE 102 via 5GBS 222 (and possibly via other intermediate entities in 5G CN 234 thatare not shown in FIG. 2), IP and SCTP may be used as transport protocolsbetween LS 226, any intermediate entities in 5G CN 234 and 5G BS 222,whereas other transport protocols such as the 3GPP Packet DataConvergence Protocol (PDCP) and 3GPP Radio Link Control (RLC) may beused (among others) between 5G BS 222 and UE 102. In that case, 5G BS222 may perform protocol conversion between SCTP and IP received from 5GCN 234 and PDCP and RLC sent to UE 102. In some embodiments, protocolconversion by an intermediate entity at an application level may alsooccur.

System 200 includes the UE 102 and another UE 103 that may be similar toor the same as UE 102 in terms of its capabilities. Other UEs similar toor the same as UEs 102 and 103 may also be present but are not shown forsimplicity. UEs 102 and 103 may support wireless access according to a5G radio interface, a 3GPP NR radio interface and possibly one or moreother radio interfaces such as LTE, IEEE 802.11 WiFi, UMTS, GSM, BT etc.UEs 102 and 103 may be able to acquire and measure one or more TPS orPRS signals transmitted by one or more of 5G BS 220, 5G BS 222 and 5G TB224 to enable location of UE 102 and/or UE 103. UEs 102 and 103 mayfurther be able to acquire and measure SPS signals transmitted by one ormore SVs 160 (e.g. GNSS SVs) to enable location of UE 102 and/or UE 103.

Although elements in system 200 such as UE 102, UE 103, 5G BS 220, 5G BS222 and 5G TB 224 are all described herein as supporting a 5G radiointerface such as a 3GPP 5G NR radio interface and as exchanging TPSsignals and control signaling using the 5G or 5G NR radio interface, thevarious techniques and embodiments described herein are to be understoodas being applicable to support of other types of radio interface bythese elements such as a future 6G radio interface, a 2G, 3G or 4G radiointerface (e.g. GSM, UMTS, LTE), an 802.11 WiFi radio interface or tocombinations of different radio interfaces in a heterogeneous network.

System 200 includes a serving network for UE 102 that includes a 5G corenetwork (CN) 224 and a 5G RAN that includes a 5G base station (BS) 220,a 5G BS 222, a 5G transmission beacon (TB) 224 and a location serverfunction (LSF) 232. Additional 5G BSs may be present that are not shownin FIG. 2 for simplicity. The serving network for UE 102 may include oneor more other RANs 218, each supporting some other radio accesstechnology (RAT) such as LTE, IEEE 802.11 WiFi, UMTS, GSM etc. The 5G CN234 may include a GMLC 216 and may be associated with a location server(LS) 226. The LS 226 may be part of 5G CN 234 or accessible from 5G CN234 (e.g. connected to 5G CN 234) and belonging to the operator for 5GCN 234. 5G CN 234 may include other elements not shown in FIG. 2. Forexample, 5G CN 234 may contain an MME (e.g. a 5G MME) similar to or thesame as MME 108 in system 100, an SGW similar to or the same as SGW 112in system 100, a PDG similar to or the same as PDG 114 in system 100and/or an HSS similar to or the same as HSS 145 in system 100. 5G CN 234may contain other elements such as a Mobility Management Function (MMF)and a Session Management Function (SMF) that perform the mobilitymanagement functions and session management functions, respectively,normally performed by an MME such as MME 108.

In some embodiments, 5G CN 234 may include an IP Multimedia Subsystem(IMS) (not shown in FIG. 2) that may be used to establish a voice call(e.g. an emergency voice call) or a data session originated by orterminated to UE 102. An IMS in 5G CN 234 may include a LocationRetrieval Function (LRF) that may support location related functionssimilar to GMLC 216 in terms of providing location services to externalclients such as providing a location for UE 102 to an external client(e.g. an external client that is a public safety answering point). Insome embodiments, an LRF included in an IMS in 5G CN 234 may connect toLS 226 when LS 226 supports a UP location solution (e.g. while LS 226 isa SUPL SLP) and/or may connect to GMLC 216 while LS 226 supports acontrol plane location solution.

5G BS 220 and/or 5G BS 222 may provide wireless communication access toUE 102 according to a 5G radio interface or 3GPP NR radio interface andmay comprise a serving BS for UE 102. 5G BS 220 and 5G BS 222 mayperform similar functions to eNBs 104 and 106 in system 100, except forsupporting a 5G or NR radio interface. 5G BS 220 and/or 5G BS 222 mayfurther transmit TPS and/or PRS signals to UE 102 to support downlinklocation of UE 102 (e.g. according to OTDOA or ECID) and/or may measureTPS and/or PRS signals transmitted by UE 102 to enable uplink locationof UE 102 (e.g. according to UTDOA or ECID). A 5G TB 224, possibly inthe same RAN as 5G BS 220 and 5G BS 222, may transmit TPS and/or PRSsignals to UE 102 to further support downlink location of UE 102 (e.g.according to OTDOA or ECID).

A location server function (LSF) 232 may support positioning of UE 102using (i) uplink measurements of UE 102 obtained and provided by 5G BS220, 5G BS 222 and/or by separate LMUs (not shown in FIG. 2) and/or (ii)downlink measurements obtained and provided by UE 102. In this context,a “location server function” as referred to herein means an apparatusthat is capable of communicating with a UE to support one or moreoperations for estimating a location of the UE. In an embodiment, alocation server function may comprising one or more processors executingcomputer-readable instructions to support one or more operations forestimating a location of a UE including, for example, providingpositioning assistance data, computing estimates of locations of clientUE devices based, at least in part, on measurements obtained from theclient UE devices, requesting client UEs to obtain measurements for usein computing estimated locations of the client UE devices, forwardingestimated locations of client UE devices to other entities (e.g., forresponses to E911 events), just to provide a few examples. As describedherein with respect to particular implementations, a location serverfunction may be integrated as part of the processing resources of anentity configured to perform a base station function within an RAN. Inother implementations, a location server function may comprise astand-alone entity within a RAN that operates separately from basestations that server UES in the RAN. It should be understood, however,that these are merely examples of features of a location serverfunction, and that claimed subject matter is not limited in thisrespect. Downlink measurements obtained and provided by UE 102 mayinclude measurements of TPS and PRS signals transmitted by 5G BS 220, 5GBS 222 and/or 5G TB 224 and/or measurements of navigation signalstransmitted by SVs 160. LSF 232 may be a standalone entity or may bepart of a 5G BS or 5G TB such as 5G BS 220, 5G BS 222 or 5G TB 224. AnLSF 232 that is implemented as part of a BS or TB is referred to as“integrated LSF” herein, or as an “LSF integrated in a BS” or “LSFintegrated in a TB”, in either case respectively. An LSF integrated in aBS may also be referred to simply as a base station, eNodeB or by someother name that does not explicitly call out a location capability. AnLSF 232 that is implemented as a separate standalone entity is referredas a “standalone LSF” herein and may also be referred to as a locationserver or as a server. LSF 232 may also be referred to as a “locationfunction” or “location application”. A standalone LSF 232 may beconnected to one or more 5G BSs and/or 5G TBs such as 5G BS 220, 5G BS222 and 5G TB 224 via direct links, a local area network, IP routersand/or other entities. Such connections may enable standalone LS 232 toexchange signaling messages with the connected entities and/or withother entities via the connected entities. A standalone LSF 232 may alsohave a connection to 5G CN 234. A standalone LSF 232 may be enabled tocommunicate with entities in or associated with 5G CN 234, such as LS226, via a connection to 5G CN 234 and/or via other entities such as 5GBSs 220 and 222 that have connections to 5G CN 234. An LSF 232integrated in 5G BS 220, 5G BS 222 or 5G TB 224 may also be enabled tocommunicate with entities in or associated with 5G CN 234, such as LS226, by using any connection or signaling path between the entity inwhich LSF 232 is integrated and 5G CN 234. While only one LSF 232 isshown in FIG. 2, a 5G RAN may include more than one LSF. For example, 5GBS 220, 5G BS 222 and 5G TB 224 may each contain an integrated LSF.

UE 102 and UE 103 in system 200 may be in communication—for example,using D2D signaling applicable to a 5G or NR radio interface. Inaddition, UE 102 and UE 103 may be enabled to perform sidelinkpositioning wherein UE 102 acquires and measures a TPS or PRStransmitted by UE 103 and/or UE 103 acquires and measures a TPS or PRStransmitted by UE 102. As previously described, sidelink positioning mayenable a UE 102 to determine a location of another UE 103 relative to UE102 or vice versa.

5G CN 234 may support communication services for UE 102 such assupporting mobility for UE 102 and communication access by UE 102 toremote entities and the Internet. 5G CN 234 may perform similarfunctions to VPLMN EPC 130 and/or HPLMN 140 in system 100, except foralso enabling wireless access by UE 102 according to a 5G or NR radiointerface. 5G CN 234 may be a serving PLMN for UE 102 and may, in somecases, also be the HPLMN for UE 102.

LS 226 may support location services on behalf of UE 102 and may supporta control plane location solution and/or a user plane location solution.LS 226 may be similar to or the same as E-SMLC 110 while supporting acontrol plane location solution. LS 226 may function as a SUPL SLP (e.g.a D-SLP, E-SLP and/or H-SLP) while supporting a user plane locationsolution and may then be accessed by an external client (not shown inFIG. 2) using a communication link 252 (e.g. which may provide accessusing SUPL to the location of UE 102 to an external client accessibleover the Internet). LS 226 may be similar to or the same as H-SLP 118 insystem 100 while supporting SUPL.

In an embodiment, LS 226 and standalone LSF 232 may be parts of the samephysical location server (e.g. may be separate software elements orprocesses or separate hardware components for the same physical server).This embodiment may reduce network complexity and cost by enablingefficient communication between LSF 232 and LS 226 in which controlsignaling exchanged between LSF 232 and LS 226 is exchanged internallywithin the same physical location server and in which data (e.g. alocation context and/or a location configuration for UE 102) can beshared by and accessible to both LSF 232 and LS 226.

GMLC 216 may provide location access to UE 102 (e.g. via LS 226)according to a control plane location solution on behalf of one or moreexternal clients (not shown in FIG. 2) which may access GMLC 216 using acommunication link 256 for control plane access. GMLC 216 may be similarto or the same as V-GMLC 116 and/or H-GMLC 148 in system 100.

System 200 may support two or more different “positioning domains”. Inthis context, a “positioning domain” may define a portion of a networkincluding particular network devices that are capable of supportingpositioning operations for a UE 102 or UE 103 by exchanging signalingmessages between or among the particular network devices. Examples of apositioning domain include a “RAN domain”, “CN domain” and “Device toDevice (D2D) Domain” (also referred to as a “UE domain”). System 200 isshown in FIG. 2 as including a D2D domain 210, a RAN domain 212 and a CNdomain 214. D2D domain 210 includes UEs 102 and 103. RAN domain 212includes UE 102 as well as 5G BS 220, 5G BS 222, 5G TB 224 and LSF 232.CN domain 214 includes UE 102 as well as LS 226. Due to use of multipledomains, system 200 may be referred to as tiered domain architecture, amulti-tiered architecture, a tiered system or a tiered architecturewhere the different tiers may correspond to the different positioningdomains such as D2D domain 210, RAN domain 212 and CN domain 214.

Implementing more than one positioning domain in a network may enableimproved support for location services for UEs such as UE 102 and/or forexternal or internal clients who may be the recipients of locationinformation (e.g. location estimates) obtained for UE 102. For example,RAN domain 212 may support low latency (e.g. a low delay of a fewseconds or less in obtaining a location estimate for a UE 102), highcapacity (e.g. an ability to locate all or most UEs currently attachedto BSs and APs in RAN domain 212), and/or a high frequency of locationfor some or all UEs (e.g. such as one location every 10 seconds). Incontrast, CN domain 214 may provide a standard interface or standard setof interfaces to external clients (e.g. external users, external webservers) that enable the external clients to request locationinformation (e.g. location estimates) for one or more UEs. The standardinterfaces may correspond to those for a 3GPP control plane locationsolution (e.g. as provided by GMLC 216 using CP communication link 256)and/or those for a SUPL user plane location solution (e.g. as providedby LS 226 using SUPL communication link 252). CN domain 214 may alsosupport more accurate location of UE 102 than RAN domain 212 through useof positioning methods not supported by RAN domain 212.

In one case including but not limited to system 200, a “RAN domain” mayrefer to a positioning domain comprising a mobile device such as UE 102in combination with entities belonging to a RAN including base stationssuch as 5G BS 220 and 5G BS 222, transmission beacons such as 5G TB 224,LMUs (not shown in FIG. 2) and an LSF such as LSF 232. Because a RANdomain includes entities in a RAN, it may also be referred to moresimply as a radio access network (RAN). Here, messaging or signalingbetween or among devices in a RAN domain may be limited to wirelesssignaling or messaging between a mobile device and one or more basestations and other entities (e.g. TBs and/or an LSF) in the RAN domain,and signaling or messaging between or among base stations and otherentities (e.g. LMUs, TBs and/or an LSF) in the RAN domain. In aparticular implementation of a RAN domain, location estimates for amobile device such as UE 102 may be obtained from (i) downlink locationmeasurements made by the mobile device of TPS or PRS signals transmittedby BSs and/or TBs in the RAN domain, (ii) downlink location measurementsmade by the mobile device of other signals transmitted by entities notin the RAN domain (such as SVs 160) and/or (iii) uplink locationmeasurements of TPS or PRS signals transmitted by the mobile device madeby BSs and/or LMUs in the RAN domain, for example. A location estimatemay be obtained by an integrated or standalone LSF (e.g. LSF 232) in theRAN domain.

In one case including but not limited to system 200, a “CN domain” mayrefer to a positioning domain comprising a mobile device such as UE 102in combination with a core network such as CN 234 and including one ormore location servers such as LS 226 that are in or associated with thecore network. Because a CN domain includes entities in a CN, it may alsobe referred to more simply as a core network (CN). Here, messaging orsignaling between or among devices in a CN domain may include signalingor messaging between a mobile device and one or more location serversand/or other entities in the CN domain. Additional signaling ormessaging between a location server in the CN domain and one or moreentities in a RAN domain may also be supported. For example, thissignaling or messaging may allow a location server in the CN domain,such as LS 226, to request and obtain location information (e.g.location measurements and/or a location estimate) for a mobile devicesuch as UE 102 from one or more entities in the RAN domain, such as LSF232, 5G BS 220 and/or 5G BS 222.

A location server in the CN domain, such as LS 226, may be enabled toobtain: (i) downlink measurements made by a mobile device, such as UE102, of TPS or PRS signals transmitted by entities in the RAN domain,such as BS 220 and TB 224, (ii) downlink measurements obtained by themobile device of TPS or PRS signals transmitted by other RANs such asother RANs 218, and/or (iii) downlink measurements of navigation signalstransmitted by SVs such as SVs 160.

A location server in a CN domain, such as LS 226, may be furtherconfigured to request and obtain location information (e.g. uplinkand/or downlink location measurements and/or a location estimate) for amobile device, such as UE 102, from other RANs such as other RANs 218. Alocation server in a CN domain, such as LS 226, may combine the locationinformation received from the mobile device (e.g. UE 102), the RANdomain (e.g. RAN domain 212) and/or other RANs (e.g. other RANs 218) todetermine a location estimate for the mobile device. A location serverin a CN domain, such as LS 226, may support a control plane locationsolution and/or a user plane location solution—e.g. as describedpreviously for LS 226. A location server in a CN domain, such as LS 226,may be enabled to configure or otherwise control the performance oflocation services in a RAN domain (e.g. RAN domain 212) and/or D2Ddomain (e.g. D2D domain 210)—e.g. by configuring particular types oflocation service to be performed in the RAN domain by an LSF (e.g. LSF232) or in the D2D domain by a UE (e.g. UE 102).

A “D2D domain” (or a “UE domain”) may refer to peer devices, such as UEs102 and 103, capable of exchanging signaling or messaging in one or morewireless links established between the peer devices and without anintervening device (e.g., base station). In a particular implementation,devices in a D2D domain, such as UEs 102 and 103, may also be part of aRAN domain, such as RAN domain 212, and/or a CN domain, such as CNdomain 214, and may employ sidelink positioning as described previouslyto obtain relative and/or absolute locations of one another.

In the example system 200 in FIG. 2, RAN domain 212 may support locationof UE 102 using only downlink and/or only uplink measurements of 5G TSPand/or PRS signals. In an embodiment, RAN domain 212 may also supportlocation of UE 102 using other downlink measurements obtained by UE 102such as of TPS and/or PRS signals transmitted by other RANs 218 and/orSVs 160. Location support by RAN domain 212 may be provided to both anauthenticated UE 102 and an unauthenticated UE 102. The location supportmay include assisting UE 102 to obtain its own location (e.g. using UEbased position methods) and/or obtaining a location for UE 102 using UEassisted and/or network based position methods and providing thislocation to UE 102. For an authenticated UE 102, the network (e.g. RANdomain 212 and/or CN domain 214) may know a public identity (e.g. aMobile Station International Subscriber Directory Number (MSISDN))and/or a private identity (e.g. an International Mobile SubscriberIdentity (IMSI)) for the UE 102 and may have authenticated one or bothidentities as being correct. For an unauthenticated UE 102, the network(e.g. RAN domain 212 or CN domain 214) may not know a public or privateidentity for UE 102 or may know such an identity but not haveauthenticated that the identity is correct.

Within RAN domain 212, a location estimate of UE 102 may be obtained byUE 102 using one or more UE based or standalone position methods or maybe obtained by LSF 232 using one or more UE assisted and/or networkbased position methods. FIG. 2 shows the uplink and downlink TPS and PRSsignals that may be acquired and measured to support positioning of UE102 in the RAN domain 212 (via the arrows in FIG. 2) and showsassociated control signaling (e.g. signaling messages) that may beexchanged between entities in the RAN domain 212 to coordinate themeasurements (via the bold solid and bold dashed lines in FIG. 2). Forexample, control signaling 260 and/or 262 may be sent point to point(e.g. using a signaling link or signaling channel) from 5G BS 220 and/orfrom 5G BS 222, respectively, to UE 102 to: (i) request one or moredownlink location measurements or a location estimate from UE 102; (ii)provide assistance data to UE 102 to help UE 102 acquire and measuredownlink signals (e.g. TPS signals or navigation signals from SVs 160)to obtain these location measurements and/or to obtain a location fromsuch location measurements; and/or (iii) request UE 102 to transmit aTPS or PRS to be measured by 5G BS 220 and/or 5G BS 222 for uplinkpositioning.

Control signaling 260 and/or 262 may also be transmitted from UE 102 to5G BS 220 and/or 5G BS 222, respectively, to provide downlink locationmeasurements (e.g. in response to a request) or to request assistancedata. Control signaling 266 may be sent from 5G BS 220 to 5G BS 222, orvice versa, to request uplink and/or downlink location measurements ofUE 102. Control signaling 268 may be sent from 5G BS 222 to 5G TB 224 toconfigure TPS or PRS transmission from 5G TB 224. Control signaling 264,260 and/or 262 may be broadcast from 5G TB 224, 5G BS 220 and/or 5G BS222, respectively, to UE 102 to provide assistance data to UE 102 tohelp UE 102 acquire and measure TPS or PRS signals transmitted by 5G TB224, 5G BS 220 and/or 5G BS 222. For example, assistance data that isbroadcast or sent point to point may indicate when TPS or PRS signalswill be transmitted (or scheduled) and may provide characteristics ofthe TPS or PRS signals such as frequencies used, bandwidth, coding andtiming. The assistance data broadcast or sent point to point by aparticular entity (e.g. 5G TB 224, 5G BS 220 or 5G BS 222) may berestricted to assisting measurement of TPS or PRS signals transmittedonly by that entity or may also assist measurement of TPS or PRS signalstransmitted by other entities. Assistance data that is broadcast or sentpoint to point may also or instead assist measurement of othersignals—e.g. TPS or PRS signals transmitted by other RANs 218 ornavigation signals transmitted by SVs 160. In a particular embodiment,5G BS 220, 5G BS 222, and/or 5G TB 224 may broadcast assistance data forGNSS RTK—e.g. by providing the carrier phase for navigation signals forone or more SVs 160 that were recently measured by one or more GNSSreceivers at precisely known locations, such as locations co-sited withone or more of 5G BS 220, 5G BS 222, 5G TB 224 and LSF 232.

An LSF 232 integrated in a BS (e.g. 5G BS 220) may determine a locationfor UE 102 from downlink location measurements provided by UE 102,uplink measurements obtained by the BS, and/or uplink measurementsobtained by another BS and transferred to the BS of which LSF 232 is apart. A standalone LSF 232 may obtain an estimated location of UE 232from these same measurements if transferred to LSF 232 from anotherentity in RAN domain 212 such as 5G BS 220 or 5G BS 222. In this case,standalone LSF 232 may exchange signaling messages with UE 102indirectly via an intermediate BS such as 5G BS 220 or 5G BS 222 inorder to: (i) request one or more downlink location measurements or alocation estimate from UE 102; (ii) provide assistance data to UE 102 tohelp UE 102 acquire and measure downlink signals and/or obtain alocation from such location measurements; and/or (iii) request UE 102 totransmit a TPS or PRS to be measured by 5G BS 220 or 5G BS 222 foruplink positioning.

Signaling messages exchanged between a standalone LSF 232 and UE 102 viaan intermediate BS (e.g. 5G BS 220 or 5G BS 222) within RAN domain 212may undergo protocol conversion by the intermediate BS to transform oneor more protocols (e.g. transport protocols) used between standalone LSF232 and the intermediate BS into similar or equivalent protocols usedbetween the intermediate BS and UE 102 over the 5G or 3GPP NR radiointerface. Such a protocol conversion may perform conversion for bothdirections of message transfer. A standalone LSF 232 may also provideassistance data to 5G BS 220, 5G BS 222 and/or 5G TB 224 for laterprovision by point-to-point or by broadcast messaging to UE 102. Forexample, the assistance data may include any of the assistance datatypes previously described herein for RAN domain 212.

Within RAN domain 212, control signaling 270, 272 and/or 274 may also beexchanged between 5G BS 220, 5G BS 222 and/or 5G TB 224, respectively,and a standalone LSF 232 to enable determination of a location for oneor more of 5G BS 220, 5G BS 222 and 5G TB 224. For example, 5G BS 220and 5G BS 222 may have accurate known locations due to a previous sitesurvey or use of GPS location but 5G TB 224 may be a low cost deviceinstalled by an operator without an initially known accurate location.5G TB 224 may then acquire and measure TPS or PRS signals transmitted by5G BS 220 and/or 5G BS 222 (and possibly from other BSs not shown inFIG. 2) and may obtain location measurements (e.g. of RSTD, RTT, AOA)which may be transferred to standalone LSF 232 as part of controlsignaling. LSF 232 may then compute an estimated location of 5G TB 224and may transmit this estimated location to 5G TB 224 and/or to LS 226for later use as assistance data to locate a UE 102 that obtainslocation measurements for TPS or PRS signals transmitted by 5G TB 224.An LSF 232 integrated in 5G BS 220 or 5G BS 222 may perform similarfunctions to obtain an estimated location of a 5G TB 224.

RAN domain 212 may support positioning of some or all UEs (such as UE102) in the coverage area of BSs in RAN domain 212 on a continuousand/or autonomous basis. For example, RAN domain 212 (e.g. a standaloneLSF 232 and/or an integrated LSF 232 in RAN domain 212) may periodically(e.g. every 10 minutes) obtain the locations of some or all served UEssuch as UE 102 and/or obtain the locations of UEs such as UE 102 whencertain trigger events (also referred to as trigger conditions) occur.For example, a trigger event may occur when (i) UE 102 changes servingcell (e.g. moves from being served by 5G BS 220 to being served by 5G BS222), or (ii) UE 102 radio coverage degrades (e.g. UE approaches theborder of a serving cell) as indicated by either UE 102 receiving lowsignal strength and/or low signal quality from a serving BS (e.g. 5G BS220), or a serving BS (e.g. 5G BS 220) receiving low signal strengthand/or low signal quality from UE 102. This periodic and/or triggeredlocation may be managed and configured by CN domain 214 (e.g. by LS 226)or may be supported autonomously by RAN domain 212 without anyconfiguration and management by CN domain 214.

RAN domain 212 may be implemented and/or designed or optimized for highvolume positioning (e.g. to support UEs belonging to the Internet ofThings (IoT)), low latency and/or high signaling efficiency.

RAN domain 212 may support periodic location of a UE 102, triggeredlocation of a UE 102 (e.g. as previously described) and/or on demandlocation of a UE 102 at one or more different times.

A “location configuration” of a UE as referred to herein meansparameters indicative of conditions or events under which one or moreoperations or actions supporting determination of an estimated locationof the UE is to occur. In an example implementation, a location contextof UE 102 may be stored in RAN domain 212 such as in a standalone LSF232, an LSF 232 integrated in a serving 5G BS 220 for UE 102 or in aserving 5G BS 220 without an LSF. The location configuration may includeinformation (e.g. parameters) that defines: (i) whether the UE 102 is tobe located periodically and, if so, an associated periodicity, (ii)whether UE 102 is to be located if certain trigger events occur and ifso what are the associated trigger events (e.g. such as UE 102 moving toa new cell or receiving degraded radio coverage), (iii) whether ondemand a location of UE 102 is to be supported and, if so which internalor external clients are enabled to request on demand location, and/or(iv) a quality of service (QoS) for locating UE 102 (e.g. definedseparately for each of (i), (ii) and (iii)) in terms of locationaccuracy and/or response time and latency. The location configurationfor UE 102 may be provided to RAN domain 212 by CN domain 214 (e.g. byLS 226), or may be provided by Operations and Maintenance (O&M), or maybe preconfigured in RAN domain 212 and may then possibly be the same forall UEs served by RAN domain 212. The location configuration for UE 102may depend on the location capabilities of UE 102 (e.g. may depend onwhich position methods are supported by UE 102) and/or on subscriptioninformation for UE 102. For example, a location configuration for UE 102may define frequent periodic location and/or triggered location for UE102 if UE 102 supports position methods that have low latency and/or ifUE subscribes to obtaining its location frequently, and may defineaccurate location of UE 102 if UE 102 supports accurate positionmethods.

A “location context” of a UE as referred to herein means one or moreparameters characterizing current or past locations of the UE. In anexample implementation, a location context may be stored in RAN domain212 for UE 102 such as in a standalone LSF 232, an LSF integrated in aserving 5G BS 220 for UE 102 or in a serving 5G BS 220 without an LSF.The location context may include information (e.g., parameters) that isassociated with the current location or recent locations of UE 102 andmay include: (i) the last known (e.g. most recently obtained) locationof UE 102, (ii) the identity (ID) of the current or last known servingcell for UE 102, (iii) the ID for the current or last known serving BSor serving AP for UE 102, (iv) one or more previous locations, previousserving cell IDs and/or previous serving BS or AP IDs for UE 102, (v)some or all of the most recent location measurements obtained by UE 102in the case of downlink measurements and/or obtained by one or more BSsand/or LMUs in the case of uplink measurements, (vi) previous uplinkand/or downlink location measurements for UE 102, (vii) informationrelated to GNSS SVs measured by UE 102 such as visible SVs, SV codephase and/or carrier phase measurements, or SV Doppler measurements,(viii) other location related measurement information obtain by UE 102or by BSs and APs in RAN 212 for UE 102, (ix) details of ongoinglocation measurements currently in progress for UE 102 (e.g. such adownlink measurements currently being obtained by UE 102), and/or (x)timestamps providing the times and possibly the dates when some or allof the different types of information in the location context (e.g. lastknown location, previous location measurements) were obtained.

In some embodiments, the location context for UE 102 may include thelocation configuration for UE 102. The location context for UE 102 maybe useful in providing a previous location estimate or a locationhistory for UE 102 to an external client (e.g. a user or web server)when UE 102 cannot be currently positioned (e.g. due to not beingaccessible from RAN domain 212 such as if out of radio coverage or in apower saving mode). The location context for UE 102 may also be used byRAN 212 to support a “warm start” or “hot start” if locating UE 102 byknowing in advance roughly where UE 102 is located which maysignificantly reduce latency and/or resources used for positioning (suchas by avoiding measurements of TPS signal from or by BSs that aredistant from UE 102). The location context for UE 102 may be furtherused to improve network operation by enabling RAN domain 212 or otherentities (e.g. 5G CN 234) to determine a suitable serving cell andserving BS for UE 102, a suitable carrier frequency and/or if handoveror cell change may be needed.

Either or both of the location context and location configuration for UE102 may be transferred from one BS to another or from one LSF to anotherwithin RAN domain 212 to support mobility of UE 102 as UE 102 moves tonew serving cells supported by RAN domain 212. The location context andpossibly the location configuration for UE 102 may also be transferredto CN domain 214 by RAN domain 212 (e.g. by LSF 232 or 5G BS 220) whenUE 102 is no longer attached to RAN domain 212 (e.g. no longer has asignaling connection to a BS in RAN domain 212 or is otherwise in idlestate). The location context and location configuration for UE 102 (iftransferred) may be stored by CN domain 214 (e.g. may be stored by LS226 or by another entity in CN domain 214 such as an MME, a 5G MME or anentity similar to an MME). At a later time, if UE 102 is again attachedto RAN domain 212, the location context and location configuration (ifstored) may be transferred back to RAN domain 212 (e.g. to a new servingBS for UE 102 or to an LSF associated with or integrated in the servingBS) to assist in supporting location for UE 102.

Location results obtained by RAN domain 212 for UE 102 (e.g. all or partof a location context for UE 102 or separate location estimates for UE102 obtained by RAN domain 212) may be used to help support handover andcell selection for UE 102 and may also be used, along with similarresults for other UEs, for, dynamic optimization of RAN domain 212,network planning, network analytics, vehicle to vehicle signaling andservices and be accessible to the CN domain 214, LS 226 and/or externalclients.

The LSF 232 may support location services for UEs such as UE 102 servedby or able to access BSs in RAN domain 212. LSF 232 may be restricted tosupporting location services only for UEs in a certain coverage areasuch as UEs served by a particular BS when LSF 232 is integrated in theBS or UEs served by some set of BSs when LSF 232 is a standalone LSFwith an association with (e.g. connections to) this set of BSs. LSF 232may also be able to support location services for all UEs served by orable to access RAN domain 212. RAN domain 212 may contain a number of(e.g. two or more) LSFs that may be load shared among UEs served by orable to access RAN domain 212 and/or may be assigned to different setsof UEs based, for example, on supporting UEs only in certain coverageareas as previously described and/or supporting only UEs that supportcertain position methods. LSF 232 may store the location contexts andlocation configurations for some or all UEs served by LSF 232. LSF 232may coordinate the location of served UEs (e.g. UE 102) according torequirements in the location configuration for each UE. For example, LSF232 may instigate location of UE 102 periodically and/or when certaintrigger conditions occur according to periodic location and/or triggeredlocation information requirements in the location context for UE 102.

An LSF 232 may also support on demand location requests from a UE 102which may apply when a UE 102 is authenticated and/or when UE 102 isunauthenticated. To support on demand location of UE 102, LSF 232 maysend assistance data to UE 102, may enable UE 102 to access broadcastassistance data (e.g. by providing a ciphering key to UE 102 whenbroadcast assistance data is ciphered), and/or may obtain a location forUE 102 using UE assisted and/or network based position methods and thensend the obtained location to UE 102. LSF 232 may interact, byexchanging control signaling, with BSs (e.g. 5G BS 220 and 5G BS 222) inRAN domain 212 in order to coordinate and obtain uplink locationmeasurements for one or more UEs (e.g. UE 102) and/or downlink locationmeasurements made by the UEs and provided by the UEs to the BSs. Thelocation measurements may be used to obtain locations for the UEs.

LSF 232 may interact, by exchanging control signaling, with a locationserver in the CN domain 214 (e.g. LS 226) if CN domain 214 is present tosupport location and may assist the location server to locate a UE 102by obtaining and returning location measurements for the UE 102 to thelocation server. LSF 232 may enable location of served UEs such as UE102 with low latency, high capacity and/or high volume by being close tothe served UEs, wherein control signaling to support location of theserved UEs remains within RAN domain 212 and does not need to travelover long signaling links (which may be expensive) or through many, ifany, intermediate entities. LSF 232 may also facilitate coupling of andinteraction between CN domain 214 and RAN domain 212 by providing aconvenient focal point for access to the locations of UEs by entities inCN domain 214 such as LS 226.

The CN domain 214 in system 200 may support some functions and controlsignaling that are similar to that described for system 100 in FIG. 1.This may be of benefit in enabling CN domain 214 to provide the same orsimilar location services to external clients and to UEs as thatprovided by system 100. This may enable a network operator to migratefrom location services support for UEs with LTE access, as exemplifiedby system 100, to location services support for UEs with 5G or 3GPP NRradio access, as exemplified by system 200, and may also enablecoexistence of both sets of services for an operator with a network ornetworks that support both LTE (4G) access and 5G or NR access.

Within CN domain 214, location server 226 may support exchange ofcontrol signaling 242 with 5G BS 220 and/or exchange of controlsignaling 244 with 5G BS 222 which may enable LS 226 to send and receivelocation related information to and from 5G BS 220 and/or 5G BS 222.This location related information may include a request for locationinformation for UE 102 sent from LS 226 to 5G BS 220 or 5G BS 222 (e.g.a request for a location estimate or uplink and/or downlink locationmeasurements for UE 102) and/or may include a request for a locationcontext for UE 102. The location related information may also include alocation configuration and/or a location context for UE 102 sent by LS226 to 5G BS 220 or 5G BS 222. The location related information mayfurther include location information for UE 102 (e.g. a locationestimate or uplink and/or downlink location measurements) or a locationcontext for UE 102 sent by 5G BS 220 or 5G BS 222 to LS 226 (e.g. ifrequested by LS 226). LS 226 may use any uplink and/or downlink locationmeasurements received from 5G BS 220 and/or 5G BS 222 to help determinea current location for UE 102.

Control signaling 242 and/or 244 may also enable LS 226 to send andreceive the same location related information (e.g. as describedpreviously) to and from LSF 232, if LSF 232 is integrated in either 5GBS 220 or 5G BS 222 or if control signaling 242 or 244 is forwarded (orrelayed) by 5G BS 220 or 5G BS 222, respectively, to and from astandalone LSF 232. Any forwarding (or relaying) of control signaling242 or 244 by 5G BS 220 or 5G BS 222 may include protocol conversion(e.g. for transport protocols) as previously described and/or mayinclude protocol conversion at an application level, wherein controlsignaling exchanged between standalone LSF 232 and 5G BS 220 and 5G BS222 uses a different application protocol to control signaling 242 and244 exchanged between LS 226 and 5G BS 220 and 5G BS 222.

LS 226 may further exchange control signaling 248 with 5G TB 224,control signaling 242 with 5G BS 220 and/or control signaling 244 with5G BS 222 to enable LS 226 to (i) send and configure information fortransmitted PRS or TPS signals (e.g. PRS or TPS bandwidth, frequencies,codes, time scheduling, duty cycle, muting, signal timing and/orsynchronization) in 5G TB 224, 5G BS 220 and/or 5G BS 222, respectively;(ii) request and subsequently receive information for transmitted PRS orTPS signals (e.g. PRS or TPS bandwidth, frequencies, codes, timescheduling, duty cycle, muting, signal timing and/or synchronization) in5G TB 224, 5G BS 220 and/or 5G BS 222, respectively; and/or (iii)request and subsequently receive information related to the locations of5G TB 224, 5G BS 220 and/or 5G BS 222, respectively (e.g. locationcoordinates or measurements made by 5G TB 224, 5G BS 220 and/or 5G BS222, respectively, of PRS or TPS signals transmitted by other BSs and/orTBs which may enable LS 226 to compute locations for 5G TB 224, 5G BS220 and/or 5G BS 222, respectively).

In some embodiments, control signaling 242, 244 and/or 248 may use the3GPP LPPa protocol which may include certain messages and/or parametersthat support positioning for 5G or NR radio access by a UE 102. Inaddition, control signaling 242, 244 and/or 248 may be transferredbetween LS 226 and 5G TB 224, 5G BS 220 and/or 5G BS 222, respectively,via one or more intermediate entities in CN 234 (not shown in FIG. 2)such as a serving MME for UE 102 or an entity similar to a serving MMEthat supports 5G or NR radio access for UE 102.

LS 226 may exchange control signaling 240 with other RANs 218 to enableLS 226 to request and subsequently receive location related measurementsfor UE 102 from other RANs 218. Control signaling 240 may be similar toor the same as LPPa signaling 162 in system 100 in the case of LTEaccess being supported by other RANs 218.

LS 226 may exchange control signaling 246 with UE 102. Control signaling246 may be similar to or the same as, and/or may be transferred in thesame or similar way as, LPP/LPPe signaling 160 in system 100 when LS 226supports a control plane location solution to locate or provideassistance data to UE 102. Control signaling 246 may be similar to orthe same as, and/or may be transferred in the same or similar way as,SUPL signaling 164 in system 100 when LS 226 is an SLP (e.g. H-SLP,D-SLP or E-SLP) and supports the SUPL user plane location solution tolocate or provide assistance data to UE 102. Thus, control signaling 246may include LPP and/or LPPe messages including the message typesdescribed in Table 1. Control signaling 246 may enable LS 226 to requestand/or receive the location capabilities of UE 102 from UE 102, receivea request for assistance data from UE 102, send assistance data to UE102 (e.g. if requested by UE 102), request location measurements or alocation estimate from UE 102 and receive location measurements or alocation estimate from UE 102 (e.g. if first requested by LS 226).Control signaling 246 may support a number of position methods to enableLS 226 to locate UE 102 such as GNSS, Assisted GNSS (A-GNSS), OTDOAapplicable to 5G or NG radio access, ECID as applicable to 5G or NGradio access, WiFi positioning, sensor based positioning, Bluetooth orBTLE based positioning. Control signaling 246 may be transferred betweenLS 226 and UE 102 via 5G BS 222 (or 5G BS 220) and one or moreintermediate entities in CN 234 (not shown in FIG. 2) such as a servingMME for UE 102 or an entity similar to a serving MME that supportsmobility management and/or session management for 5G or NR radio accessfor UE 102.

CN domain 214 may comprise an evolution of a CN with location supportfor a UE with 3G (e.g. WCDMA) and/or 4G (e.g. LTE) wireless access, suchas VPLMN EPC 130 and/or HPLMN 140 exemplified in system 100 in the caseof LTE, but may include additional capabilities such as an ability toconfigure location support in RAN domain 212 and obtain locationinformation for UE 102 from RAN domain 212 as previously described. CNdomain 214 may include one or more location servers, such as LS 226,which may be part of or associated with CN 234, and be able to supportthe OMA SUPL location solution and/or a 3GPP control plane locationsolution. There may be multiple location servers in CN domain 214. EachLS (e.g. LS 226) may support load sharing of location support for UEs,location support for a specific geographic area or a specific networkcoverage area, one or more position methods that may be distinct fromposition methods supported by other location servers, and/or somecombination of these. In some networks, no location server 226 may bepresent and instead, location support of a UE 102 may be provided onlyby RAN domain 212 and/or by D2D domain 210.

A location server 226 in CN domain 214 may support functions of anE-SMLC for location of a UE with 4G LTE access and may then performactions that are the same as, or similar to, E-SMLC 110 in system 100.Location server 226 may also or instead support functions of an SLP(e.g. an H-SLP, D-SLP or E-SLP) for location of a UE with 4G LTE accessand may then perform actions the same as or similar to H-SLP 118 insystem 100.

CN domain 214 and LS 226 may support location of UEs such as UE 102 withlower volume, lower capacity, higher latency, higher accuracy and/orhigher reliability than RAN domain 112. CN domain 214 and LS 226 mayalso support location of UE 102 in particular scenarios: (i) inassociation with an emergency call from UE 102; (ii) while UE 102 isable to access and make location related measurements for multiple RANssuch as both RAN domain 212 and other RANs 218; and/or (iii) whilepositioning methods not associated with measuring TPS or PRS signals areused such as with positioning using A-GNSS or sensors.

CN domain 214 and/or LS 226 may further enable support for locationprivacy for UE 102 and may interact with external clients (e.g. via GMLC216 or directly via LS 226) to enable external clients to request andreceive location information (e.g. location estimates) for UE 102 and torequest additional services such as periodic or triggered locationreporting for UE 102.

CN domain 214 (e.g. LS 226 and/or other elements in CN domain 214 suchas an MME or an entity similar to an MME) may be enabled to controllocation support in RAN domain 212 by providing a location configurationto RAN domain 212 (e.g. to LSF 232, 5G BS 220 and/or 5G BS 222) for UE102 or for a group of (e.g. all) UEs accessing RAN domain 212. Thelocation configuration that is provided may include requirements andinstructions for locating UE 102 or a group of UEs (e.g. all UEsaccessing RAN domain 212), as discussed previously. CN domain 214 (e.g.LS 226 and/or other elements in CN domain 214 such as an MME or anentity similar to an MME) may further be enabled to request and receivea location context and/or location information for UE 102 (and/or or fora group of UEs accessing RAN domain 212), wherein the location contextincludes information related to current and previous locations for UE102 (or for a group of UEs) as previously discussed and wherein thelocation information includes a current location estimate for UE 102 (orfor each of a group of UEs).

CN domain 214 (e.g. LS 226 and/or other elements in CN domain 214 suchas an MME or an entity similar to an MME) may be further enabled tosupport location for an authenticated UE 102 and possibly for anunauthenticated UE 102 (e.g. if location is requested for anunauthenticated UE 102 that is making an emergency call).

CN domain 214 (e.g. LS 226 or some other entity in CN domain 214) maymaintain a location context and/or location configuration for UE 102that may be similar to, or the same as, the location context and/orlocation configuration, respectively, that may be maintained for UE 102in RAN domain 112 (e.g. by LSF 232) as described previously. A locationcontext and/or location configuration for UE 102 maintained by CN domain214 may be used to support location services for UE 102. A locationcontext for UE 102 maintained by CN domain 214 may include locationrelated information (e.g. current and previous cell IDs, current andprevious location related measurements) applicable to other RANs 218 ifUE 102 has current or previous access and/or current or previousvisibility to BSs and/or APs in other RANs 218. A location configurationfor UE 102 maintained by CN domain 214 may enable support for (i)geofencing (e.g., to enable a report to an external client when UE 102enters, leaves or remains within a particular geographic area), (ii)tracking (e.g., to enable reporting of a location history for UE 102 toan external client), (iii) navigation (e.g., to enable reporting ofnavigation directions to UE 102), and/or (iv) other location services.

Part of all of a location configuration maintained by CN domain 214 forUE 102 may be transferred to RAN domain 212 (e.g. to 5G BS 220, 5G BS222 or LSF 232) to provide RAN domain 212 with a location configurationfor UE 102. Similarly, part or all of a location context for UE 102 maybe transferred from CN domain 214 to RAN domain 212 or vice versa to (i)serve as an initial location context for UE 102, (ii) add to an existinglocation context for UE 102 and/or (iii) assist with mobility supportfor UE 102 wherein a location context in a serving BS for UE 102 or inan LSF associated with UE 102 is transferred to the CN domain 214 whenUE 102 moves to a new serving BS or becomes temporarily detached fromRAN domain 212 and is later transferred back to a new serving BS or newLSF associated with UE 102 (e.g. when UE 102 later reattaches to RANdomain 212).

D2D domain 210 may be an extension or part of RAN domain 212 in someembodiments or may be a separate autonomous domain. D2D domain 210 mayhelp support location of UEs 102 and 103 if one or both UEs are out ofradio coverage of RAN domain 212 and CN domain 214, unable to access RANdomain 212 and CN domain 214 (e.g. due to lack of an appropriatesubscription) and/or if RAN domain 212 or CN domain 214 haveinsufficient capacity and resources to support location adequately forall UEs. UEs 102 and 103 may exchange control signaling 280 to discoverone another and/or to coordinate location support. For example, UE 102and/or UE 103 may measure TPS or PRS signals transmitted from the otherUE (e.g. may measure RSSI, RTT, AOA, RSRP and/or RSRQ) and may request,transfer and/or assist these measurement by exchanging control signaling280. UE 102 (and UE 103) may coordinate with other UEs (not shown inFIG. 2) to obtain or enable additional measurements of TPS or PRSsignals transmitted by these UEs and/or additional measurements by theseUEs of TPS or PRS signals transmitted by UE 102 (and UE 103). Thelocation measurements may be returned to LSF 232 and/or to LS 226 toenable determination of a location for UE 102 (and UE 103) by LSF 232and/or LS 226 or may be used by UE 102 (and UE 103) to determine alocation or relative location of UE 102 (and UE 103). The locationmeasurements and determined locations for UE 102 and UE 103 may be usedto help support direct signaling being UEs 102 and 103 (e.g., LTE-Director WiFi-Direct), discovery by UE 102 of UE 103 and/or vice versa, and/orvarious peer to peer communication services.

FIG. 3 shows a signaling flow 300 applicable to system 200 that enablessupport of location services by D2D domain 210, RAN domain 212 and CNdomain 214 in system 200. Signaling flow 300 comprises three sets ofsignaling interactions 310, 320 and 340 that may each occur in isolationor in association with one another. Signaling interactions 310 supportpositioning of UE 102 using the D2D domain 210; signaling interactions320 support positioning of UE 102 using the RAN domain 212; andsignaling interactions 340 support positioning if UE 102 using the CNdomain 214. For ease of interpretation of FIG. 3, control signalingbetween pairs of entities is shown using arrows with an alloweddirection of transfer shown by an arrow (e.g. with a double arrowindicating allowance of bidirectional signaling transfer). Radiofrequency TPS or PRS signals sent between pairs of entities are shownusing bold arrows where an arrow again indicates a possible transmissiondirection. The arrows can correspond to point to point transfer (e.g.directional transfer of PRS/TPS signals using an antenna array ortargeted transfer of control signaling) as well as use of broadcast.

For simplicity (and as also applicable to FIG. 2), only one instance ofcontrol signaling and/or one instance of TPS signaling (which may beunidirectional or bidirectional) is shown in FIG. 3 between certainpairs of interacting entities. However, this is not intended to implythat one and only one signaling message would be transferred from oneentity to another in the case of control signaling or that one and onlyone type of TPS signal would be transmitted from one entity to the otherin the case of TPS signals. Instead, the arrows are to be understood asindicating the transfer of a plurality of zero, one or more signalingmessages from one entity to the other in the direction shown by an arrowin the case of control signaling and the transmission of zero, one ormore TPS signals from one entity to the other in the direction shown byan arrow in the case of TPS signals. In addition, where bidirectionaltransfer is indicated (using a double arrow), the signaling messages andthe TPS signals sent in each direction may be the same, similar, ordifferent. Furthermore, in some embodiments, control signaling and/orTPS transmission may be sent from one entity to another that is notindicated in FIG. 3.

The numbered elements in FIG. 3 (UE 102, UE 103, 5G BS 220, 5G TB 224,LSF 232 and LS 226) correspond to the like numbered elements in FIG. 2and may perform exactly the same functions. Each small circle containingan “X” in FIG. 3 indicates a possible event at an entity where alocation estimate for UE 102 or possibly for UE 103 may be determined bythe entity (e.g. using location measurements and other informationpreviously received in control signaling). Other elements in system 200are omitted from FIG. 3 for clarity. The control signaling andtransmission of TPS or PRS signals shown in FIG. 3 largely mirrors thatshown in FIG. 2 but is shown in more detail in order to better clarifysupport of location services by D2D domain 210, RAN domain 212 and CNdomain 214 in system 200.

Signaling interactions 310 for D2D domain 210 include transmission ofone or more TPS signals 312 for a 5G or NR radio interface from UE 102to UE 103 and/or from UE 103 to UE 102. TPS signals 312 may be sent onrequest (e.g., if one UE sends a control signaling request to the other)or if triggered by receipt of other TPS signals 312 or for otherreasons. UE 102 or/and UE 103 that receives TPS signals 312 may makelocation related measurements of TPS signals 312, for examplemeasurements of RSSI, RTT, AOA, RSRP, RSRQ, and/or RSTD as describedpreviously. Signaling interactions 310 also include transmission of oneor more control signaling messages 314 that may correspond to messagesfor a 5G or NR radio signaling layer 3. Control signaling 314 may beused by UE 102 and/or UE 103 to instigate and coordinate sidelinkpositioning of one or both UEs in which one or both UEs obtainmeasurements of TPS signals 312 transmitted by the other UE and possiblysend the measurements to the other UE using control signaling 314.Following exchange of TPS signals 312 and control signaling 314, UE 103may determine a location for UE 103 and/or for UE 102 at 316 and/or UE102 may determine a location for UE 102 and/or for UE 103 at 318, usingmeasurements of TPS signals 312 that were made locally and/ormeasurements of TPS signals 312 that were sent by the other UE.

Signaling interactions 320 for RAN domain 212 include the TPS signals,control signaling and determination of a location for UE 102 shown inFIG. 3. 5G TB 224 may transmit one or more TPS signals 322 (e.g. maybroadcast the signals) which may be for a 5G or NR radio interface. TheTPS signals 322 may be sent at fixed periodic intervals or may be sentat irregular intervals (e.g. if UEs such as UE 102 are to bepositioned). Sending of TPS signals 322 may be controlled by LSF232—e.g. if positioning of a UE 102 is requested. UE 102 may makelocation related measurements of TPS signals 322 which may includemeasurements of RSSI, RTT, AOA, RSRP, RSRQ and/or RSTD measurements.

Control signaling 324 sent by 5G TB 224 to UE 102 (e.g. sent viabroadcast or multicast) may provide different types of assistance datato UE 102 to assist UE 102 to measure TPS signals 322, to assist UE 102to determine a location from measurements of TPS signals 322 and/or toassist UE 102 to measure other TPS signals and signals from othersources (e.g. GNSS SVs) and possibly compute an estimated location of UE102 from such measurements. As an example, a transmission schedule forthe future transmission times of TPS signals 322 may be provided to UE102 and possibly other UEs by 5G TB 224 using control signaling 324. AUE 102 receiving the transmission schedule for TPS signals 322 maydetermine times to assign resources to measure TPS signals 322. Controlsignaling 324 sent by 5G TB 224 to UE 102 may also provide other detailsof TPS signals 322 such as the frequency or frequencies, bandwidth,coding and/or muting pattern (if any) for TPS signals 322.

Control signaling 324 sent by 5G TB 224 may also or instead provideother location related information such as location coordinates for 5GTB 224, the precise current time (e.g. a GPS time or a CoordinatedUniversal Time (UTC)), time synchronization or time differenceinformation for TPS signals 322 (e.g. relative to GPS time or TPS timingof 5G TB 224), and/or similar TPS and location related information (e.g.such as location coordinates and TPS parameters) for other 5G TBs and/or5G BSs such as 5G BS 220. Control signaling 324 may also or insteadprovide assistance data related to other types of positioning such as byproviding information useful for GNSS positioning such as GNSS ephemerisdata, GNSS almanac data, SV Doppler shifts, SV carrier phasemeasurements at a GNSS reference receiver applicable to RTK (e.g. at aGNSS reference receiver co-sited with 5G TB 224), ionosphericpropagation data, and/or tropospheric propagation information.

After obtaining measurements of TPS signals 322 and possibly of othersignals (e.g., GNSS SV navigation signals), UE 102 may use the obtainedmeasurements and possibly any assistance data received in controlsignaling 324 to determine or help determine a location for UE 102 at325.

Similarly to 5G TB 224, 5G BS 220 may transmit (e.g., via multicast orbroadcast) one or more TPS signals 326 and control signaling 328 to ortowards UE 102. TPS signals 326 and control signaling 328 sent by 5G BS220 may be similar to or the same as TPS signals 322 and controlsignaling 324, respectively, sent by 5G TB 224 as described previously,but with control signaling 328 providing information primarily for TPSsignals 326 and for 5G BS 220 rather than primarily for TPS signals 322and for 5G TB 224. UE 102 may obtain location related measurements ofTPS signals 326 sent by 5G BS 220 that be similar to or the same aslocation related measurements described previously for TPS signals 322.However, unlike interaction with 5G TB 324, UE 102 may transmit one ormore TPS signals 326 that may be measured by 5G BS 220 or by an LMUassociated with 5G BS 220. UE 102 transmission of TPS signals 326 may becontrolled (e.g. scheduled) by 5G BS 220 using control signaling 328 orby standalone LSF 232 using control signaling 330 and 328 as describedlater.

In an embodiment, control signaling 328 and/or control signaling 324 maybe performed according to a Radio Resource Control (RRC) protocol (e.g.for 5G or NR radio access).

5G BS 220 may obtain measurements, such as of RSSI, RTT, AOA, RSRPand/or RSRQ, for TPS signals 326 transmitted by UE 102. 5G BS 220 (or anLSF integrated in 5G BS 220) or standalone LSF 232 may use controlsignaling 328 or control signaling 328 and 330, respectively, to controlor coordinate (i) measurements by UE 102 of TPS signals 326 transmittedby 5G BS 220, and/or (ii) TPS signals 326 transmitted by UE 102 that aremeasured by 5G BS 220. UE 102 may use control signaling 328 to send to5G BS 220 any measurements made by UE 102 of (i) TPS signals 326transmitted by 5G BS 220 and/or (ii) TPS signals 322 transmitted by 5GTB 224. In addition or instead, 5G BS 220 (or an LSF integrated in 5G BS220) may use control signaling 328 to send to UE 102 any measurementsmade by 5G BS 220 of TPS signals 326 transmitted by UE 102. While usedto schedule measurements by UE 102 of TBS signals 322 or 326 or totransfer measurements from UE 102 to 5G BS 220 or from 5G BS 220 to UE102, control signaling 328 may be used in a point to point manner (e.g.if there is an association or signaling connection between UE 102 and 5GBS 220) rather than in a broadcast message. Following these measurementsand possible transfer of measurements, UE 102 or 5G BS 220 (or an LSFintegrated in 5G BS 220) may determine a location for UE 102 using thesemeasurements (that were obtained locally or received using controlsignaling 328) at 332 or 334, respectively.

In some implementations, 5G BS 220 may contain an integrated LSF inwhich case 5G BS 220 (or the LSF integrated in 5G BS 220) may assist UE102 to obtain a location for UE 102 or may obtain a location for UE 102itself, as just described for RAN domain signaling interactions 320.Other functions for an integrated LSF in 5G BS 220, such as support of alocation context or location configuration for UE 102, may be the sameas or similar to functions described further on for a standalone LSF232.

In some implementations, a standalone LSF 232 may be deployed in RANdomain 212 with connections (e.g. direct or indirect) to other entitiesin RAN domain 212 such as 5G BS 220 and 5G TB 224. Standalone LSF 232may use these connections to exchange control signaling 330 and/or 331with 5G BS 220 and/or 5G TB 224, respectively. Standalone LSF 232 maysend control signaling 330 to 5G BS 220 to configure TPS signals 326sent (e.g. broadcast) by 5G BS 220 such as by providing TPSconfiguration information including transmission scheduling, bandwidth,frequencies, coding, muting etc. Standalone LSF 232 may also sendassistance data to 5G BS 220 in control signaling 330 to be later sentby 5G BS 220 to UE 102 in control signals 328 and corresponding to oneor more of the different types of assistance data described previouslythat may be sent by 5G BS 220 or by 5G TB 224 to UE 102. Standalone LSF232 may also send a request to 5G BS 220 in control signaling 330 forconfiguration information (e.g. parameters) for TPS signals 326 sent by5G BS 220 and/or for other information related to 5G BS 220 such aslocation coordinates. 5G BS 220 may then return the requestedinformation in control signaling 330 to standalone LSF 232. Analogous tothis interaction with 5G BS 220, standalone LSF 232 may use controlsignaling 331 to send configuration information for TPS signals 322 to5G TB 224, to send assistance data to 5G TB 224 and/or to request andreceive configuration information for TPS signals 322 sent by 5G TB 224and/or other information related to 5G TB 224.

Standalone LSF 232 may also or instead use control signaling 330 torequest or schedule measurements of TPS signals 322 and/or 326 by UE102, to request and receive measurements from UE 102 and/or to sendassistance data to UE 102. In this case, a signaling message sent bystandalone LSF 232 to 5G BS 220 using control signaling 330 may beforwarded or relayed by 5G BS 220 to UE 102 using control signaling 328and possibly with protocol conversion by 5G BS 220. The forwarding at 5GBS 220 may use point to point means to send control signaling 328 to UE102 (e.g. if there is an association or signaling connection between UE102 and 5G BS 220) or may use broadcast to send information to UE 102and possibly to other UEs—e.g. in the case of assistance data sent bystandalone LSF 232. Transfer of control signaling in the reversedirection from UE 102 to standalone LSF 232 via 5G BS 220 withforwarding or relaying by 5G BS 220 and possibly with protocolconversion by 5G BS 220 may occur in a similar manner. Standalone LSF232 may then use control signaling 330 and 328 (e.g. with forwarding orrelaying by 5G BS 220) to (i) send assistance data to UE 102 (e.g.assistance data to help UE measure TPS signals 322 and/or 326 sent by 5GTB 224 and/or 5G BS 220, respectively, and/or assistance data forlocation sources such as GNSS or RTK); (ii) schedule or requestmeasurements by UE 102 of TPS signals 322 and/or 326 sent by 5G TB 224and/or 5G BS 220, respectively, and/or of other signals sent by othersources such as GNSS SVs; and/or (iii) receive measurements from UE 102and made by UE 102 of TPS signals 322 and/or 326 sent by 5G TB 224and/or 5G BS 220, respectively.

In some embodiments, UE 102 may use control signaling 328 to sendpositioning capabilities of UE 102 to 5G BS 220. The positioningcapabilities of UE 102 may indicate the position methods, locationmeasurements (e.g. of RSSI, RTT, AOA, S/N, RSTD, RSRP, and/or RSRQ)and/or assistance data supported by UE 102. 5G BS 220 may forward anypositioning capabilities received from UE 102 to either an integratedLSF 232 in 5G BS 220 or to a standalone LSF 232 using control signaling330. In some embodiments, UE 102 may send positioning capabilities of UE102 to 5G BS 220 if requested by 5G BS 220 or by an integrated LSF 232in 5G BS 220 using control signaling 328, or if requested by astandalone LSF 232 using control signaling 330 and 328 relayed through5G BS 220. Standalone LSF 232 or an LSF 232 integrated in 5G BS 220 mayuse any positioning capabilities of UE 102 to determine, or helpdetermine, assistance data to be sent to UE 102 and/or particularlocation measurements (e.g. of TPS signals 322 and 326 or of signalsfrom SVs 160) to be requested from UE 102.

Standalone LSF 232 may also or instead use control signaling 330 to (i)send assistance data to 5G BS 220 (e.g. assistance data to help 5G BS220 measure TPS signals 326 sent by UE 102), (ii) schedule or requestmeasurements by 5G BS 220 (or an LMU associated with 5G BS 220) of TPSsignals 326 sent by UE 102, and/or (iii) receive measurements from 5G BS220 and made by 5G BS 220 of TPS signals 326 sent by UE 102. Followingreceipt, as just described, of location related measurements made by UE102 and/or made by 5G BS 220, standalone LSF 232 may compute a locationfor UE 102 at 336 based at least in part on these measurements.

As described previously, standalone LSF 232 or an LSF integrated in 5GBS 220 may have a location configuration for UE 102 and/or a locationcontext for UE 102, one or both of which may be initially provided by CNdomain 214 (e.g. by LS 226). The various actions described previouslyfor standalone LSF 232 and 5G BS 220 (or an LSF integrated in 5G BS 220)with regard to scheduling location measurements by UE 102, sendingassistance data to UE 102 and/or requesting and receiving locationmeasurements made by UE 102, or made by 5G BS 220 of UE 102, may bepartly or completely defined by the location configuration for UE 102.For example, the location configuration may define or indicate (i) if alocation estimate for UE 102 is to be obtained (e.g. periodically and/orwhen certain trigger events occur); (ii) which types of assistanceshould be or can be sent to UE 102 (e.g. assistance data to assistmeasurement of TPS signals 322 and/or 326 or assistance data to assistUE 102 measurements and possibly location computation for GNSS or RTK);(iii) which types of location measurements can or should be requestedfrom UE 102 and/or from 5G BS 220; and/or (iv) a particular level oflocation accuracy and/or latency may be needed for any estimatedlocation of UE 102.

Standalone LSF 232 or an integrated LSF in 5G BS 220 may also storelocation related information for UE 102 in a location context, which mayinclude location estimates obtained for UE 102, location measurementsobtained from or of UE 102, a current serving BS for UE 102, and/or acurrent serving cell for UE 102. Standalone LSF 232 or an integrated LSFin 5G BS 220 may use a location context for UE 102 to improve locationsupport for UE 102 (e.g. by knowing in advance which BSs can makemeasurements of UE 102 or can be measured by UE 102) and to assistlocation services to external clients—e.g. by enabling a locationhistory or a last known location for UE 102 to be provided to anexternal client.

Signaling interactions 340 for CN domain 214 may include TPS signals,control signaling and determination of an estimated location of UE 102shown in FIG. 3. 5G TB 224 may transmit one or more TPS signals 352(e.g. may broadcast the signals) which may correspond to TPS signals 322described previously and may be measured by UE 102 as describedpreviously for UE 102 measurement of TP signals 322. 5G BS 220 maytransmit one or more TPS signals 356 (e.g. may broadcast the signals)which may correspond to TPS signals 326 described previously when sentby 5G BS 220. TPS signals 356 may be also measured by UE 102 asdescribed previously for UE 102 measurement of TP signals 326transmitted by 5G BS 220. UE 102 may transmit TPS signals 344 which maycorrespond to TPS signals 326 described previously when sent by UE 102.TPS signals 344 may be also measured by 5G BS 220 (or by an LMUassociated with 5G BS 220) as described previously for 5G BS 220measurement of TPS signals 326 transmitted by UE 102. Transmissionand/or measurement of TPS signals 344, 352 and/or 356 may be controlledat least in part by CN domain 214 such as by LS 226 associated with CNdomain 214. In the description that follows, it is assumed that controlof measurement and/or transmission of TPS signals 344, 352 and/or 356 aswell as other interactions are performed by LS 226, but in someembodiments, at least some of these actions may be performed by otherelements in CN domain 214 such as by an MME, a PDG or other elements in5G CN 234 similar to or corresponding to these.

LS 226 may exchange control signaling 342 with standalone LSF 232,control signaling 346 and 354 with 5G BS 220 (or with an integrated LSFin 5G BS 220), control signaling 358 with UE 102, and control signaling350 with 5G TB 224. Control signaling 342, 346, 350, 354 and 358 may becontrol signaling for a control plane location solution (e.g. when LS226 supports a control plane solution) or control signaling for a userplane location solution (e.g. when LS 226 is a SUPL SLP). As describedpreviously, control signaling for a user plane solution may betransferred as data messaging within a network using such protocols asIP and TCP while control signaling for a control plane solution istransferred using existing network interfaces and protocols andappearing as control signaling rather than as data to immediateentities.

In an embodiment, in order to improve signaling efficiency for CN domain214, control signaling 342, 346, 350, 354 and/or 358, when sent as partof a control plane location solution, may be transferred (e.g. viaintermediate entities) similar to or the same as data using, forexample, IP, UDP, TCP and/or SCTP as transport protocols. Thisembodiment may also be used in RAN domain 212 to transfer controlsignaling 330 and 331 between standalone LSF 232 and 5G BS 220 and 5G TB224, respectively, the same as data. In this embodiment, controlsignaling 342, 346, 350, 354 and/or 358 (and/or control signaling 330and 331) may only be visible to endpoints for transmission and reception(e.g. may be visible to UE 102, LSF 232, 5G BS 220, 5G TB 224 and LS226), but may be seen and transferred as data by intermediate entitiessuch as (i) an MME or entity similar to an MME in CN domain 214 or (ii)5G BS 220. This embodiment may reduce impacts to support controlsignaling 342, 346, 350, 354 and/or 358 by CN domain 214 and/or RANdomain 212, may reduce signaling delay and latency and/or may increasenetwork capacity by enabling a greater volume of control signalingsupporting location for more UEs. In addition, the embodiment may reducedifferences between control plane location support and user planelocation support at UE 102 and LS 226, thereby reducing implementationimpact and cost when both location solutions are supported. Theembodiment may also facilitate support of control signaling 342, 346,350, 354 and/or 358 by LS 226 when LS 226 supports user plane location,which may enable additional location support from RAN domain 212 for LS226 as described later herein. This embodiment may contrast withexisting support of user plane location as described previously forsystem 100 where an SLP such as H-SLP 118 may not normally be enabled toaccess location information and/or control location activity in a RANdomain such as RAN domain 212.

Although supporting control signaling 342, 346, 350, 354 and/or 358similar to data in the case of a control plane location solution mayreduce differences with a user plane solution such as SUPL, the twosolutions may still remain different in some aspects. For example,access from an external client to LS 226 when supporting control planelocation may be via a GMLC such as GMLC 216 or via a GMLC and an LRF. Incontrast, access to LS 226 when supporting a user plane locationsolution may be direct, via an LRF but not a GMLC, or via the Internet(e.g. using the OMA MLP protocol). Such different types of access,though adding to network implementation, may be useful to operators whoneed to support existing control plane and/or user plane locationsolutions for other radio access types such as 4G LTE as previouslyexemplified in system 100, because it may enable the same type of commonaccess from an external client regardless of whether a UE 102 has 5Gradio access as in system 200 or 4G radio access as in system 100 orsome other radio access. This common access may enable common locationsupport to an external client regardless of the radio access type beingused by UE 102. For example, in the case of control plane location, anexternal client may send a location request for UE 102 to GMLC 216 insystem 200 (e.g., directly or via one or more other GMLCs and possiblythe Internet). GMLC 216 may then determine the serving network and aserving node (e.g., an MME such as MME 108 for 4G LTE access or a MobileSwitching Center (MSC) for 2G or 3G access) for UE 102 (e.g., byquerying HSS 145). GMLC 216 may then forward the location request to theserving node in the serving network which may forward the locationrequest to an LS such as E-SMLC 110 when UE 102 has 4G LTE accessaccording to system 100 or LS 226 when UE 102 had 5G access according tosystem 200. The LS can then obtain a location for UE 102 (e.g., asdescribed previously for system 100 in the case of LTE access and asdescribed previously for system 200 in the case of 5G radio access) andreturn the location to the external client via the serving node and GMLC216. Such a solution may support a location request from an externalclient for several types of cellular access (e.g. 2G, 3G, 4G or 5G) byUE 102 and without requiring the external client to know which cellularaccess type is currently being used by UE 102.

LS 226 may send control signaling 342 to standalone LSF 232 or controlsignaling 346 to an integrated LSF in 5G BS 220 in order to transfer toeither entity location configuration for UE 102, a location context forUE 102, location information for UE 102 (e.g. in response to a request)or a request for one or more of these items. Similarly, standalone LSF232 may send control signaling 342 to LS 226, or an integrated LSF in 5GBS 220 may send control signaling 346 to LS 226, in order to transfer toLSF 226 a location configuration for UE 102, a location context for UE102, location information for UE 102 (e.g. in response to a request fromLS 226) or a request for one or more of these items. A locationconfiguration and location context for UE 102 may be as describedpreviously and may be used by standalone LSF 232 or an integrated LSF in5G BS 220 as described previously for signaling interactions 320 in RANdomain 212.

LS 226 may create, update and/or store a location configuration for UE102 based at least in part on subscription data for UE 102 (e.g. whichmay be configured in LS 226 for UE 102 or may be provided to LS 226 byanother element in CN domain 214 such as an MME or an entity similar toan MME). LS 226 may also or instead create, update and/or store alocation configuration for UE 102 based on network preferences for allUEs (e.g. configured in LS 226) or based on a location service requestfor UE 102—e.g. received directly or indirectly (e.g. via GMLC 216) froman external client or an internal client belonging to or associated withCN domain 214. The location configuration may include informationdescribed previously such as requirements for periodic location,triggered location and/or location accuracy for UE 102.

LS 226 may also or instead create, update and/or store a locationcontext for UE 102 which may contain location information obtained forUE 102 by LS 226 such a last known location, previous locations,previous location measurements, a last known and/or previous servingcell IDs, and/or last known and/or previous serving BS IDs. LS 226 mayrequest a location context for UE 102 from an LSF in RAN domain 212(e.g. standalone LSF 232) as just described and may combine the receivedlocation context with any location context already stored by LS 226 forUE 102.

LS 226 may transfer a stored location configuration and/or a storedlocation context for UE 102 to standalone LSF 232 or to an integratedLSF in 5G BS 220 for use in RAN domain 212 as previously described forsignaling interactions 320 in RAN domain 212. LS 226 may selectstandalone LSF 232 or an integrated LSF in 5G BS 220 based on 5G BS 220being a serving BS for UE 102 and/or (if selecting standalone LSF 232)standalone LSF 232 being associated with (e.g. connected to) a servingBS for UE 102. Alternatively, LS 226 may select standalone LSF 232 or anintegrated LSF in 5G BS 220 based on load sharing requirements and/orpositioning and location service capabilities of standalone LSF 232 oran integrated LSF in 5G BS 220 (e.g. such as support of certain positionmethods and/or support of certain location services like periodic ortriggered location). LS 226 may also receive a location context fromstandalone LSF 232 or an integrated LSF in 5G BS 220 and later transferthe location context to another (or the same) standalone LSF orintegrated LSF in order to support mobility of UE 102 (e.g. cell changeor handover) and detachment of UE 102 from, and later re-attachment ofUE 102 to, RAN domain 212 and CN domain 214 (e.g. if UE 102 temporarilyloses radio coverage or goes into idle state to reduce network resourceand/or battery power usage).

LS 226 may request and receive location information from standalone LSF232 or an integrated LSF in 5G BS 220 using control signaling 342 or346, respectively. The location information may include a locationestimate for UE 102, a last known location for UE 102, a locationhistory for UE 102 and/or location measurements for UE 102. Locationmeasurements for UE 102 may be obtained by UE 102 of TPS signals 352and/or 356 or of other signals such as GNSS signals or may be obtainedby 5G BS 220 (and/or by other BSs or LMUs) of TPS signals 344transmitted by UE 102. LS 232 may use received location information todetermine or help determine a location estimate for UE 102 which maythen be provided to an external client or internal client of CN domain214 (not shown in FIG. 3). Actions of LS 226 may be triggered in part bylocation requests received by LS 232 (e.g. according to a control oruser plane location solution) from an external client or internal clientof CN domain 214.

LS 226 may send control signaling 354 (and/or 346) to 5G BS 220 toconfigure TPS signals 356 (and/or 326) sent (e.g. broadcast) by 5G BS220 to UEs such as UE 102. Control signaling 354 sent by LS 226 mayprovide configuration information for TPS signals 356 such as includingtransmission scheduling, bandwidth, frequencies, coding, muting etc. LS226 may also or instead send assistance data to 5G BS 220 in controlsignaling 354 (and/or 346) to be later sent by 5G BS 220 to UE 102 incontrol signals 328. The configuration information and assistance datamay correspond to that described previously as being sent in someembodiments from a standalone LSF 232 to 5G BS 220. For example, theassistance data may include information to assist a UE 102 to measureTPS signals 356 (and/or 326) transmitted by 5G BS 220, to measure TPSsignals transmitted by other BSs and TBs (e.g. 5G TB 224) and/or tomeasure other signal sources such as GNSS SVs. LS 226 may also send arequest to 5G BS 220 in control signaling 354 (and/or 346) forconfiguration information (e.g. parameters) for TPS signals 356 (and/or326) transmitted by 5G BS 220 and/or for other information related to 5GBS 220 such as location coordinates. 5G BS 220 may then return therequested information in control signaling 354 (and/or 346) to LS 226.Analogous to this interaction with 5G BS 220, LS 232 may use controlsignaling 350 to: (i) send configuration information for TPS signals 352(and/or 322) to 5G TB 224; (ii) send assistance data to 5G TB 224 foronward transmission (e.g. via broadcast) to UEs such as UE 102; and/or(iii) request and receive configuration information for TPS signals 352(and/or 322) transmitted by 5G TB 224 and/or for other informationrelated to 5G TB 224. The interactions using control signaling betweenLS 226 and 5G BS 220 and between LS 226 and 5G TB 224 may be the same asor similar to the interactions using control signaling betweenstandalone LSF 232 and 5G BS 220 and between standalone LSF 232 and 5GTB 224, respectively, in terms of the information transferred

If LS 226 is to obtain a location for UE 102 (e.g. due to receiving alocation request for UE 102 from an external client or an internalclient in CN domain 214), LS 226 may send control signaling 346 to 5G BS220 to request 5G BS 220 to measure TPS signals 344 transmitted by UE102 and/or to measure other uplink signals transmitted by UE 102 notnormally intended for positioning (e.g. signals used primarily totransfer control information, voice or data). The measurements requestedfrom 5G BS 220 may include measurements of RSSI, RTT, AOA, RSRP, and/orRSRQ, to name a few examples. LS 226 may also or instead send controlsignaling 346 to 5G BS 220 to request measurements made by UE 102 ifsuch measurements are available to 5G BS 220 (e.g., due to having beensent by UE 102 to 5G BS 220 in control signaling 328). The requestedmeasurements made by UE 102 may include measurements of TPS signals 356transmitted by 5G BS 220 and/or of other signals transmitted by 5G BS220 (e.g., such as signals used to transfer control information ordata), and/or (ii) measurements made by UE 102 of signals transmitted byother BSs and/or TBs. 5G BS 220 may then send control signaling 346 toLS 226 to return any measurements made by 5G BS 220 that were requestedby LS 226, and/or return any measurements made by UE 102 that areavailable to 5G BS 220 and that were requested by LS 226. LS 226 may usemeasurements returned by 5G BS 220 in control signaling 346 to determineor help determine a location estimate for UE 102 at 348.

Similar to obtaining measurements from 5G BS 220 to obtain a locationfor UE 102, LS 226 may send control signaling 358 to UE 102 to requestUE 102 to measure (i) TPS signals 356 transmitted by 5G BS 220; (ii)other signals transmitted by 5G BS 220 (e.g. such as signals used totransfer control information or data); (iii) TPS and/or other signalstransmitted by other BSs and/or other TBs (e.g. 5G TB 224); and/or (iv)signals transmitted by other sources such as BSs and/or TBs in otherRANs 218 or SVs 160. The measurements requested by LS 226 may supportone or more position methods including ECID, OTDOA, A-GNSS, WiFi,Bluetooth, sensors, to name a few examples. In the case of ECID, therequested measurements may include measurements of RSSI, RTT, S/N, AOA,RSRP and/or RSRQ for TPS or other signals sent by BSs and TBs such as 5GBS 220 and 5G TB 224. In the case of OTDOA, the requested measurementsmay include measurements of RSTD and/or TOA for TPS or other signalssent by BSs and TBs such as 5G BS 220 and 5G TB 224. In the case ofA-GNSS, the requested measurements may include measurements ofpseudoranges, code phase values and/or carrier phase values for one ormore SVs 160 in one or more GNSSs. To assist UE 102 to obtain therequested measurements and/or possibly to assist UE 102 to compute alocation estimate using these measurements, LS 226 may send assistancedata to UE 102 in control signaling 358.

To know in advance the positioning capabilities of UE 102 (e.g.indicating which location measurements, position methods and assistancedata are supported by UE 102), LS 226 may exchange control signaling 358with UE 102 to request and obtain the positioning capabilities of UE 102or may receive the positioning capabilities of UE 102 unsolicited fromUE 102 in control signaling 358. UE 102 may obtain some or all of thelocation measurements requested by LS 232. UE may then compute alocation estimate for UE 102 at 360 and/or may return the locationmeasurements, or a computed location estimate, to LS 232 using controlsignaling 358, after which LS 226 may determine a location for UE 102 at362 using the returned location measurements or location estimate.

In an embodiment, control signaling 342, 346, 350 and/or 354 may use the3GPP LPPa protocol with additional messages and/or additional parameterscompared to existing LPPa. For example, the additional messages and/orparameters in LPPa may be used to support positioning methods,information transfer and/or retrieval and configuration of TPS signalsfor a 5G or 5G NR radio access by UEs such as UE 102.

In another embodiment, control signaling 358 may use the 3GPP LPPpositioning protocol and/or the combined LPP/LPPe positioning protocolwhich may include additional messages and/or additional parameterscompared to existing LPP and/or existing LPPe. For example, theadditional messages and/or parameters in LPP and/or LPPe may be used torequest and return location measurements, request and return assistancedata, transfer unsolicited assistance data, request and return UEpositioning capabilities for position methods associated with a 5G or 5GNR radio access by UEs such as UE 102.

FIG. 4 is a flow diagram for a process 400 for providing positioningservices to a UE accessing a RAN according to an embodiment. Thepositioning services may include obtaining an estimated location for theUE. The UE may correspond to UE 102 or UE 103 in FIGS. 1-3. In oneimplementation, the process 400 may be performed by one or moreprocessors of a base station, access point or a location server functionin a RAN as discussed previously. In an implementation, the process 400may be performed by certain elements in FIGS. 2-3 comprising (i) astandalone LSF 232, (ii) an LSF 232 integrated in 5G BS 220 or in 5G BS222, or (iii) 5G BS 220 or 5G BS 222. For example, a base station orintegrated LSF having features shown by device 704 of FIG. 7 may performthe actions for process 400, at least in part, by execution ofinstructions stored on memory 722 by processing unit 720. Furthermore,communication interface 730 in combination with processing unit 720 maybe used to transmit and receive messages/signals/control signaling indata links in support of providing location services to UEs in a RANdomain. In an alternative implementation, the process 400 may beperformed by a standalone LSF 232 acting as a standalone entity. Forexample a standalone LSF having features shown by device 904 of FIG. 9may perform actions for process 400, at least in part, by execution ofinstructions stored on memory 922 by processing unit 920. Furthermore,communication interface 930 in combination with processing unit 920 maybe used to transmit and receive messages/signals/control signaling indata links in support of providing location services to a UE. It shouldbe understood that the example structures for performing actions setforth in process 400 are merely example structures, and that claimedsubject matter is not limited to these particular structures.Furthermore, the actions described for process 400 may be performed invarious orders and actions may be omitted or added. For ease ofdescription, process 400 is described as being performed by an LSF (e.g.a standalone LSF 232 or an LSF 232 integrated in 5G BS 220) but may alsobe performed by a BS (e.g. 5G BS 220) as just described.

At block 402 for process 400, the LSF exchanges a plurality of one ormore first signaling messages with the UE, one or more first signalingmessages comprising: (i) a location measurement received from the UE;(ii) a request sent to the UE for the location measurement; (iii)assistance data sent to the UE; or (iv) some combination of these. Forcase (i) where a location measurement is received from the UE, the LSFmay be enabled to determine a location estimate for the UE based atleast in part on the location measurement. For case (iii) whereassistance is sent to the UE, the assistance data may assist the UE toobtain the location measurement. One or more first signaling messagesmay correspond to control signaling 328 in signaling flow 300 in thecase of an LSF integrated in 5G BS 220 or control signaling 328 pluscontrol signaling 330 in signaling flow 300 in the case of a standaloneLSF 232, as described previously herein.

At block 404 for process 400, the LSF exchanges a plurality of one ormore second signaling messages with a location server associated with acore network. One or more second signaling message may comprise locationinformation for the UE, a request for the location information for theUE, a location configuration for the UE, a request for the locationconfiguration for the UE, a location context for the UE, a request forthe location context for the UE, or some combination of these. One ormore second signaling messages may correspond to control signaling 342in signaling flow 300 in the case of a standalone LSF 232 or to controlsignaling 346 and/or 354 in the case of an LSF integrated in 5G BS 220.

When the LSF corresponds to a standalone LSF, such as standalone LSF232, one or more first signaling messages may be exchanged with the UEusing an intermediate base station such as 5G BS 220. In that case, oneor more first signaling messages may undergo protocol conversion at theintermediate base station. For example, this may be as describedpreviously for signaling flow 300, where standalone LSF 232 sends andreceives control signaling 330 via standalone 5G BS 220, with standalone5G BS 220 forwarding or relaying the control signaling to or from UE 102as control signaling 328. 5G BS 220 may then perform protocol conversionbetween control signaling 328 and control signaling 330 (e.g. at thetransport level and/or at the application level).

The UE in process 400 may have a 5G or 3GPP NR radio interface and oneor more first signaling messages may then be exchanged, at least inpart, using the 5G or NR radio interface.

In an embodiment, the location measurement received at block 402 may beobtained by the UE and may be a measurement of received signal strengthindication (RSSI), angle of arrival (AOA), round trip signal propagationtime (RTT), reference signal time difference (RSTD), signal to noiseratio (S/N), reference signal received power (RSRP), reference signalreceived quality (RSRQ), a code phase for a satellite vehicle (SV), acarrier phase for an SV, or a location estimate for the UE.

In an embodiment, the assistance data sent at block 402 may be sent tothe UE by the LSF using broadcast or may be sent point to point to theUE.

In an optional block 406 for process 400, the LSF obtains a locationestimate for the UE based at least in part on the location measurementreceived from the UE at block 402. Block 406 may correspond to event 334or event 336 in signaling flow 300.

In an embodiment, the location information exchanged at block 404 maycomprise a location estimate for the UE, location measurements for theUE or both.

In an embodiment, the location configuration exchanged at block 404 maycomprise parameters defining periodic location of the UE, triggeredlocation of the UE, location accuracy for the UE, or some combination ofthese, as described in association with system 200 and signaling flow300.

In an embodiment, the location context exchanged at block 404 maycomprise a last known serving cell identifier (ID) for the UE, a lastknown serving base station ID for the UE, a last known location for theUE, the location measurement received at block 402, or some combinationof these, as described in association with system 200 and signaling flow300.

In an embodiment, one or more second signaling messages exchanged atblock 404 may be defined according to the Long Term Evolution (LTE)Positioning Protocol Annex (LPPa) protocol for the 3^(rd) GenerationPartnership Project (3GPP).

In an embodiment, one or more second signaling messages exchanged atblock 404 may be exchanged using the Internet Protocol (IP).

FIG. 5 is a flow diagram for a process 500 for supporting locationservices at a user equipment (UE) that may be accessing a RAN accordingto an embodiment. The location services may include obtaining a locationfor the UE. The UE may correspond to UE 102 or UE 103 in FIGS. 1-3. Forexample, a UE having features shown by mobile device 800 of FIG. 8 mayperform the actions for process 500, at least in part, by execution ofinstructions stored on memory 840 by modem processor 866, generalpurpose application processor 811 or DSP(s) 812. Furthermore, interface820 in combination with wireless transceiver 821 may be used to transmitand receive messages/signals/control signaling in support of actions forprocess 500. It should be understood that the example structures forperforming actions set forth in process 500 are merely examplestructures, and that claimed subject matter is not limited to theseparticular structures. Furthermore, the actions described for process500 may be performed in various orders and actions may be added oromitted.

At block 502 for process 500, the UE exchanges a plurality of one ormore first signaling messages with a location server function (LSF)associated with a radio access network (RAN). One or more firstsignaling messages comprises: (i) a first location measurement sent bythe UE; (ii) a request received by the UE for the first locationmeasurement; (iii) first assistance data received by the UE; or (iv)some combination of these. For case (i), the location server functionmay be enabled to determine a location estimate for the UE based atleast in part on the first location measurement. For case (iii), thefirst assistance data may assist the UE to obtain the first locationmeasurement. The LSF may be a standalone entity (e.g. a standalone LSF)or an LSF integrated in a base station or access point. The LSF maycorrespond to standalone LSF 232 or to an LSF 232 integrated in 5G BS220, as described previously for system 200 and signaling flow 300. Oneor more first signaling messages may correspond to control signaling 328in signaling flow 300 in the case of an LSF integrated in 5G BS 220 orcontrol signaling 328 plus control signaling 330 in signaling flow 300in the case of a standalone LSF 232, as described previously herein.

At block 504 for process 500, the UE exchanges a plurality of one ormore second signaling messages with a location server (LS) associatedwith a core network. One or more second signaling message may comprise asecond location measurement sent by the UE, a request received by the UEfor the second location measurement, second assistance data received bythe UE, or some combination of these. The assistance data received bythe UE in block 504 may assist the UE to obtain the second locationmeasurement. One or more second signaling messages exchanged at block504 may correspond to control signaling 358 in signaling flow 300. Thelocation server may correspond to LS 226 in system 200.

When the LSF for block 502 corresponds to a standalone entity such asstandalone LSF 232, one or more first signaling messages may beexchanged with the LSF using an intermediate base station such as 5G BS220. In that case, one or more first signaling messages may undergoprotocol conversion at the intermediate base station. For example, thismay be as described previously for signaling flow 300, where standaloneLSF 232 sends and receives control signaling 330 via 5G BS 220, with 5GBS 220 forwarding or relaying the control signaling 330 to or from UE102 as control signaling 328. 5G BS 220 may then perform protocolconversion between control signaling 328 and control signaling 330 (e.g.at the transport level and/or at the application level).

When the UE for process 500 has 5G or 3GPP NR radio access (e.g. as insystem 200), one or more first signaling messages may be exchanged, atleast in part, using the 5G or 3GPP NR radio interface.

In some embodiments of process 500, at least one of the first locationmeasurement sent by the UE at block 502 and the second locationmeasurement sent by the UE at block 504 is a measurement of receivedsignal strength indication (RSSI), angle of arrival (AOA), round tripsignal propagation time (RTT), reference signal time difference (RSTD),signal to noise ratio (S/N), reference signal received power (RSRP),reference signal received quality (RSRQ), a code phase for a satellitevehicle (SV), a carrier phase for an SV or a location estimate for theUE.

In an embodiment of process 500, the first assistance data received bythe UE at block 502 may be received in a broadcast signal (e.g. a signalbroadcast by 5G TB 224 or 5G BS 220 in the case of signaling flow 300).

In an embodiment of process 500, one or more second signaling messagesexchanged at block 504 may be defined according to the Long TermEvolution (LTE) Positioning Protocol (LPP) for the 3^(rd) GenerationPartnership Project (3GPP), the LPP Extensions (LPPe) protocol definedby the Open Mobile Alliance (OMA), or both LPP and LPPe.

FIG. 6 is a flow diagram for a process 600 for providing positioningservices to a UE accessing a RAN according to an embodiment. Thepositioning services may include obtaining a location for the UE. The UEmay correspond to UE 102 or UE 103 in FIGS. 1-3. The positioningservices may be performed by a location server in or associated with acore network such as 5G CN 234 in system 200 or a location server in orassociated with a CN domain such as CN domain 214 in system 200. In animplementation, the process 600 may be performed by LS 226 in system 200or by E-SMLC 110 or H-SLP 118 in system 100. For example, a locationserver having features shown by device 904 of FIG. 9 may perform actionsfor process 600, at least in part, by execution of instructions storedon memory 922 by processing unit 920. Furthermore, communicationinterface 930 in combination with processing unit 920 may be used totransmit and receive messages/signals/control signaling in data links insupport of providing location services to a UE. It should be understoodthat the example structures for performing actions set forth in process600 are merely example structures, and that claimed subject matter isnot limited to these particular structures. Furthermore, the actionsdescribed for process 600 may be performed in various orders and actionsmay be added or omitted.

At block 602 for process 600, the location server exchanges a pluralityof one or more first signaling messages with a UE, wherein one or morefirst signaling messages comprises a location measurement received fromthe UE, a request sent to the UE for the location measurement,assistance data sent to the UE, or some combination of these. Theassistance data sent to the UE at block 602 may assist the UE to obtainthe location measurement. One or more first signaling messages exchangedat block 602 may correspond to control signaling 358 as describedpreviously for signaling flow 300.

At block 604 for process 600, the location server exchanges a pluralityof one or more second signaling messages with a location server function(LSF) associated with a radio access network (RAN), wherein one or moresecond signaling message comprise location information for the UE, arequest for the location information for the UE, a locationconfiguration for the UE, a request for the location configuration forthe UE, a location context for the UE, a request for the locationcontext for the UE, or some combination of these. The LSF may comprise astandalone entity such as standalone LSF 232 in system 200 or maycomprise, or comprise part of, a base station or access point such as anLSF 232 integrated in 5G BS 220 or 5G BS 222 as described previously forsystem 200. One or more second signaling messages exchanged at block 604may correspond to control signaling 346 and/or 354 as describedpreviously for signaling flow 300.

The UE for process 600 may have a fifth generation (5G) or 3GPP newradio (NR) radio interface and one or more first signaling messages maybe exchanged at block 602, at least in part, using the 5G or NR radiointerface.

In an embodiment of process 600, the location measurement received fromthe UE at block 602 may be a measurement of received signal strengthindication (RSSI), angle of arrival (AOA), round trip signal propagationtime (RTT), reference signal time difference (RSTD), signal to noiseratio (S/N), reference signal received power (RSRP), reference signalreceived quality (RSRQ), a code phase for a satellite vehicle (SV), acarrier phase for an SV, or a location estimate for the UE.

At an optional block 606 in process 606 in process 600, the locationserver obtains a location estimate for the UE based at least in part onthe location measurement received at block 602 and/or the locationinformation exchanged at block 604 in the case that the locationinformation is received by the location server from the LSF. Block 606may correspond to event 348 or event 362 for signaling flow 300

In an embodiment of process 600, one or more first signaling messagesexchanged at block 602 are defined according to the Long Term Evolution(LTE) Positioning Protocol (LPP) protocol for the 3^(rd) GenerationPartnership Project (3GPP), the LPP Extensions (LPPe) protocol definedby the Open Mobile Alliance (OMA), or both LPP and LPPe.

In an embodiment of process 600, the location information exchanged atblock 604 comprises a location estimate for the UE, locationmeasurements for the UE or both.

In an embodiment of process 600, the location configuration exchanged atblock 604 comprises parameters defining periodic location of the UE,triggered location of the UE, location accuracy for the UE, or somecombination of these.

In an embodiment of process 600, the location context exchanged at block604 comprises a last known serving cell identifier (ID) for the UE, alast known serving base station ID for the UE, a last known location forthe UE, the location measurement received at block 602, the locationinformation exchanged at block 604, or some combination of these.

In an embodiment of process 600, one or more second signaling messagesexchanged at block 604 are defined according to the Long Term Evolution(LTE) Positioning Protocol Annex (LPPa) protocol for the 3^(rd)Generation Partnership Project (3GPP).

In an embodiment of process 600, one or more second signaling messagesare exchanged at block 604 using the Internet Protocol (IP).

Subject matter shown in FIGS. 7, 8 and 9 may comprise features, forexample, of a computing device, in an embodiment. It is further notedthat the term computing device, in general, refers at least to one ormore processors and a memory connected by a communication bus. Likewise,in the context of the present disclosure at least, this is understood torefer to sufficient structure within the meaning of 35 USC § 112(f) sothat it is specifically intended that 35 USC § 112(f) not be implicatedby use of the term “computing device,” “UE,” “location server,”“location server function” and/or similar terms; however, if it isdetermined, for some reason not immediately apparent, that the foregoingunderstanding cannot stand and that 35 USC § 112(f) therefore,necessarily is implicated by the use of the term “computing device,”“UE,” “location server,” “location server function” and/or similarterms, then, it is intended, pursuant to that statutory section, thatcorresponding structure, material and/or acts for performing one or morefunctions be understood and be interpreted to be described at least inFIGS. 4, 5 and 6, and corresponding text of the present disclosure.

FIG. 7 is a schematic diagram illustrating an example system 700 thatmay include one or more devices configurable to implement techniques orprocesses described above, for example, in connection with FIGS. 1-6.System 700 may include, for example, a first device 702, a second device704, and a third device 706, which may be operatively coupled togetherthrough a wireless communications network. In an aspect, first device702 may comprise a UE as shown, for example, such as UE 102 or 103 inFIGS. 1-3. Second device 704 may comprise a node in a cellular/wirelesscommunication network such as a base station or access point. Forexample second device 704 may correspond to any of 5G BS 220, 5G BS 222,5G TB 224 or an LSF 232 integrated in 5G BS 220 or 5G BS 222 asdescribed for FIGS. 2-3. Third device 706 may comprise another UE, in anaspect, such as UE 102 or UE 103 in FIGS. 1-3. Also, in an aspect,devices 702, 704 and 706 may be included in a wireless communicationsnetwork (not shown in FIG. 7) which may comprise one or more wirelessaccess points, for example, such as the networks described for FIGS.1-2. However, claimed subject matter is not limited in scope in theserespects.

First device 702, second device 704 and third device 706, as shown inFIG. 7, may be representative of any device, appliance or machine thatmay be configurable to exchange data over a wireless communicationsnetwork. By way of example but not limitation, any of first device 702,second device 704, or third device 706 may include: one or morecomputing devices or platforms, such as, e.g., a desktop computer, alaptop computer, a workstation, a server device, or the like; one ormore personal computing or communication devices or appliances, such as,e.g., a personal digital assistant, mobile communication device, or thelike; a computing system or associated service provider capability, suchas, e.g., a database or data storage service provider/system, a networkservice provider/system, an Internet or intranet serviceprovider/system, a portal or search engine service provider/system, awireless communication service provider/system; wirelesstelecommunications access terminal; or any combination thereof. Any ofthe first, second, and third devices 702, 704, and 706, respectively,may comprise one or more of an access point or a mobile device inaccordance with the examples described herein.

Similarly, a wireless communications network, as shown in FIG. 7, isrepresentative of one or more communication links, processes, orresources configurable to support the exchange of signaling and/or databetween at least two of first device 702, second device 704, and thirddevice 706. By way of example but not limitation, a wirelesscommunications network may include wireless or wired communicationlinks, telephone or telecommunications systems (e.g., LTE), data busesor channels, optical fibers, terrestrial or space vehicle resources,local area networks, wide area networks, intranets, the Internet,routers or switches, and the like, or any combination thereof. Asillustrated, for example, by the dashed lined box illustrated as beingpartially obscured of third device 706, there may be additional likedevices operatively coupled to system 700.

It is recognized that all or part of the various devices and networksshown in FIG. 7, and the processes and methods as further describedherein, may be implemented using or otherwise including hardware,firmware, software, or any combination thereof.

Thus, by way of example but not limitation, second device 704 mayinclude at least one processing unit 720 that is operatively coupled toa memory 722 through a bus 728.

Processing unit 720 is representative of one or more circuitsconfigurable to perform at least a portion of a data computing procedureor process. By way of example but not limitation, processing unit 720may include one or more processors, controllers, microprocessors,microcontrollers, application specific integrated circuits, digitalsignal processors, programmable logic devices, field programmable gatearrays, and the like, or any combination thereof.

Memory 722 is representative of any data storage mechanism. Memory 722may include, for example, a primary memory 724 or a secondary memory726. Primary memory 724 may include, for example, a random accessmemory, read only memory, etc. While illustrated in this example asbeing separate from processing unit 720, it should be understood thatall or part of primary memory 724 may be provided within or otherwiseco-located/coupled with processing unit 720.

Secondary memory 726 may include, for example, the same or similar typeof memory as primary memory or one or more data storage devices orsystems, such as, for example, a disk drive, an optical disc drive, atape drive, a solid state memory drive, etc. In certain implementations,secondary memory 726 may be operatively receptive of, or otherwiseconfigurable to couple to, a computer-readable medium 740.Computer-readable medium 740 may include, for example, anynon-transitory medium that can carry or make accessible data, code orinstructions for one or more of the devices in system 700.Computer-readable medium 740 may also be referred to as a storagemedium.

Second device 704 may include, for example, a communication interface730 that provides for or otherwise supports the operative coupling ofsecond device 704 to a wireless communications network at least throughan antenna 708. By way of example but not limitation, communicationinterface 730 may include a network interface device or card, a modem, arouter, a switch, a transceiver, and the like. In a particularimplementation, communication interface 730 may comprise a wirelesstransmitter that is configured for transmission of a TPS or PRS.

Communication interface 730 may further comprise a wireless receiverthat is configured for reception, acquisition and/or measurement of aTPS or PRS. Communication interface 730 (or a different communicationinterface for second device 704 not shown in FIG. 7) may further supportthe operative coupling of second device 704 to a wireline communicationsnetwork and/or to wired communication links that may enable seconddevice 704 to communicate with one or more other elements in a radioaccess network or in a core network such as standalone LSF 232 or LS 226in system 200.

Second device 704 may include, for example, an input/output device 732.Input/output device 732 is representative of one or more devices orfeatures that may be configurable to accept or otherwise introduce humanor machine inputs, or one or more devices or features that may beconfigurable to deliver or otherwise provide for human or machineoutputs. By way of example but not limitation, input/output device 732may include an operatively configured display, speaker, keyboard, mouse,trackball, touch screen, data port, etc.

Second device 704 may further include a time reference unit 750 that maybe configured to determine an accurate global or common time by means ofaccess to an accurate global time source, which may be provided in oneembodiment by GNSS navigation signals received at antenna 708 andacquired, measured and/or demodulated by communication interface 730.Time reference unit 750 may be used by second device 704 (e.g. bycommunication interface 730) to synchronize TPS and PRS signalstransmitted by communication interface 730 using antenna 708 to theaccurate global or common time and/or to measure the timing (e.g. TOA orRSTD) for TPS and PRS signals received by communication interface 730using antenna 708.

In a particular implementation, all or portions of actions or operationsset forth for process 400 may be executed by processing unit 720 basedon machine-readable instructions stored in memory 722. For exampleprocessing unit 720 may exchange control signaling with other entities(e.g. a location server, standalone LSF or a UE) using communicationinterface 730 in order to support actions of process 400.

FIG. 8 is a schematic diagram of a mobile device 800 according to anembodiment. UE 102 and/or UE 103 as shown in FIGS. 1, 2 and 3 maycomprise one or more features of mobile device 800 shown in FIG. 8. Incertain embodiments, mobile device 800 may comprise a wirelesstransceiver 821 which is capable of transmitting and receiving wirelesssignals 823 via wireless antenna 822 over a wireless communicationnetwork. Wireless transceiver 821 may be connected to bus 801 by awireless transceiver bus interface 820. Wireless transceiver businterface 820 may, in some embodiments be at least partially integratedwith wireless transceiver 821. Some embodiments may include multiplewireless transceivers 821 and wireless antennas 822 to enabletransmitting and/or receiving signals according to correspondingmultiple wireless communication standards such as, for example, versionsof IEEE Standard 802.11, CDMA, WCDMA, LTE, UMTS, GSM, AMPS, Zigbee,Bluetooth and a 5G or NR radio interface defined by 3GPP, just to name afew examples. In a particular implementation, wireless transceiver 821may receive and acquire a downlink signal comprising a terrestrialpositioning signal such as a PRS. For example, wireless transceiver 821may process an acquired terrestrial positioning signal sufficiently toenable detection of timing of the acquired terrestrial positioningsignal.

Mobile device 800 may also comprise SPS receiver 855 capable ofreceiving and acquiring SPS signals 859 via SPS antenna 858 (which maybe the same as antenna 822 in some embodiments). SPS receiver 855 mayalso process, in whole or in part, acquired SPS signals 859 forestimating a location of mobile device 800. In some embodiments,general-purpose processor(s) 811, memory 840, digital signalprocessor(s) (DSP(s)) 812 and/or specialized processors (not shown) mayalso be utilized to process acquired SPS signals, in whole or in part,and/or calculate an estimated location of mobile device 800, inconjunction with SPS receiver 855. Storage of SPS, TPS or other signals(e.g., signals acquired from wireless transceiver 821) or storage ofmeasurements of these signals for use in performing positioningoperations may be performed in memory 840 or registers (not shown).General-purpose processor(s) 811, memory 840, DSP(s) 812 and/orspecialized processors may provide or support a location engine for usein processing measurements to estimate a location of mobile device 800.In a particular implementation, all or portions of actions or operationsset forth for process 500 may be executed by general-purposeprocessor(s) 811 or DSP(s) 812 based on machine-readable instructionsstored in memory 840. For example general-purpose processor(s) 811 orDSP(s) 812 may process a downlink signal acquired by wirelesstransceiver 821 to, for example, make measurements of RSSI, RTT, AOA,TOA, RSTD, RSRQ and/or RSRQ.

Also shown in FIG. 8, digital signal processor(s) (DSP(s)) 812 andgeneral-purpose processor(s) 811 may be connected to memory 840 throughbus 801. A particular bus interface (not shown) may be integrated withthe DSP(s) 812, general-purpose processor(s) 811 and memory 840. Invarious embodiments, functions may be performed in response to executionof one or more machine-readable instructions stored in memory 840 suchas on a computer-readable storage medium, such as RAM, ROM, FLASH, ordisc drive, just to name a few example. The one or more instructions maybe executable by general-purpose processor(s) 811, specializedprocessors, or DSP(s) 812. Memory 840 may comprise a non-transitoryprocessor-readable memory and/or a computer-readable memory that storessoftware code (programming code, instructions, etc.) that are executableby processor(s) 811 and/or DSP(s) 812 to perform functions describedherein.

Also shown in FIG. 8, a user interface 835 may comprise any one ofseveral devices such as, for example, a speaker, microphone, displaydevice, vibration device, keyboard, touch screen, just to name a fewexamples. In a particular implementation, user interface 835 may enablea user to interact with one or more applications hosted on mobile device800. For example, devices of user interface 835 may store analog ordigital signals on memory 840 to be further processed by DSP(s) 812 orgeneral purpose processor 811 in response to action from a user.Similarly, applications hosted on mobile device 800 may store analog ordigital signals on memory 840 to present an output signal to a user. Inanother implementation, mobile device 800 may optionally include adedicated audio input/output (I/O) device 870 comprising, for example, adedicated speaker, microphone, digital to analog circuitry, analog todigital circuitry, amplifiers and/or gain control. It should beunderstood, however, that this is merely an example of how an audio I/Omay be implemented in a mobile device, and that claimed subject matteris not limited in this respect. In another implementation, mobile device800 may comprise touch sensors 862 responsive to touching or pressure ona keyboard or touch screen device.

Mobile device 800 may also comprise a dedicated camera device 864 forcapturing still or moving imagery. Camera device 864 may comprise, forexample an imaging sensor (e.g., charge coupled device or CMOS imager),lens, analog to digital circuitry, frame buffers, just to name a fewexamples. In one implementation, additional processing, conditioning,encoding or compression of signals representing captured images may beperformed at general purpose/application processor 811 or DSP(s) 812.Alternatively, a dedicated video processor 868 may perform conditioning,encoding, compression or manipulation of signals representing capturedimages. Additionally, video processor 868 may decode/decompress storedimage data for presentation on a display device (not shown) on mobiledevice 800.

Mobile device 800 may also comprise sensors 860 coupled to bus 801 whichmay include, for example, inertial sensors and environment sensors.Inertial sensors of sensors 860 may comprise, for example accelerometers(e.g., collectively responding to acceleration of mobile device 800 inthree dimensions), one or more gyroscopes or one or more magnetometers(e.g., to support one or more compass applications). Environment sensorsof mobile device 800 may comprise, for example, temperature sensors,barometric pressure sensors, ambient light sensors, camera imagers,microphones, just to name few examples. Sensors 860 may generate analogor digital signals that may be stored in memory 840 and processed byDPS(s) 812 or general purpose application processor 811 in support ofone or more applications such as, for example, applications directed topositioning or navigation operations.

In a particular implementation, mobile device 800 may comprise adedicated modem processor 866 capable of performing baseband processingof signals received and downconverted at wireless transceiver 821 or SPSreceiver 855. Similarly, modem processor 866 may perform basebandprocessing of signals to be upconverted for transmission by wirelesstransceiver 821. In alternative implementations, instead of having adedicated modem processor, baseband processing may be performed by ageneral purpose processor or DSP (e.g., general purpose/applicationprocessor 811 or DSP(s) 812). It should be understood, however, thatthese are merely examples of structures that may perform basebandprocessing, and that claimed subject matter is not limited in thisrespect.

FIG. 9 is a schematic diagram illustrating an example system 900 thatmay include one or more devices configurable to implement techniques orprocesses described above. System 900 may include, for example, a firstdevice 902, a second device 904, and a third device 906, which may beoperatively coupled together through a wireless communications network908. In an aspect, second device 904 may comprise a server or locationserver, such as LS 226 or standalone LSF 232 in system 200, or E-SMLC110 or H-SLP 118 in system 100. Also, in an aspect, wirelesscommunications network 908 may comprise one or more wireless accesspoints, for example. However, claimed subject matter is not limited inscope in these respects.

First device 902, second device 904 and third device 906 may berepresentative of any device, appliance or machine. By way of examplebut not limitation, any of first device 902, second device 904, or thirddevice 906 may include: one or more computing devices or platforms, suchas, e.g., a desktop computer, a laptop computer, a workstation, a serverdevice, or the like; one or more personal computing or communicationdevices or appliances, such as, e.g., a personal digital assistant,mobile communication device, or the like; a computing system orassociated service provider capability, such as, e.g., a database ordata storage service provider/system, a network service provider/system,an Internet or intranet service provider/system, a portal or searchengine service provider/system, a wireless communication serviceprovider/system; or any combination thereof. Any of the first, second,and third devices 902, 904, and 906, respectively, may comprise one ormore of a location server, a base station almanac server, a locationserver function, a base station, or a mobile device in accordance withthe examples described herein.

Similarly, wireless communications network 908, may be representative ofone or more communication links, processes, or resources configurable tosupport the exchange of data between at least two of first device 902,second device 904, and third device 906. By way of example but notlimitation, wireless communications network 908 may include wireless orwired communication links, telephone or telecommunications systems, databuses or channels, optical fibers, terrestrial or space vehicleresources, local area networks, wide area networks, intranets, theInternet, routers or switches, and the like, or any combination thereof.As illustrated, for example, by the dashed lined box illustrated asbeing partially obscured by third device 906, there may be additionallike devices operatively coupled to wireless communications network 908.

It is recognized that all or part of the various devices and networksshown in system 900, and the processes and methods as further describedherein, may be implemented using or otherwise including hardware,firmware, software, or any combination thereof.

Thus, by way of example but not limitation, second device 904 mayinclude at least one processing unit 920 that is operatively coupled toa memory 922 through a bus 928.

Processing unit 920 is representative of one or more circuitsconfigurable to perform at least a portion of a data computing procedureor process. By way of example but not limitation, processing unit 920may include one or more processors, controllers, microprocessors,microcontrollers, application specific integrated circuits, digitalsignal processors, programmable logic devices, field programmable gatearrays, and the like, or any combination thereof.

Memory 922 is representative of any data storage mechanism. Memory 922may include, for example, a primary memory 924 or a secondary memory926. Primary memory 924 may include, for example, a random accessmemory, read only memory, etc. While illustrated in this example asbeing separate from processing unit 920, it should be understood thatall or part of primary memory 924 may be provided within or otherwiseco-located/coupled with processing unit 920.

In a particular implementation, a digital map of an indoor area may bestored in a particular format in memory 922. Processing unit 920 mayexecute instructions to processes the stored digital map to identify andclassify component areas bounded by a perimeter of structures indicatedin the digital map.

Secondary memory 926 may include, for example, the same or similar typeof memory as primary memory or one or more data storage devices orsystems, such as, for example, a disk drive, an optical disc drive, atape drive, a solid state memory drive, etc. In certain implementations,secondary memory 926 may be operatively receptive of, or otherwiseconfigurable to couple to, a computer-readable medium 940.Computer-readable medium 940 may include, for example, anynon-transitory medium that can carry or make accessible data, code orinstructions for one or more of the devices in system 900.Computer-readable medium 940 may also be referred to as a storagemedium.

Second device 904 may include, for example, a communication interface930 that provides for or otherwise supports the operative coupling ofsecond device 904 to at least wireless communications network 908. Byway of example but not limitation, communication interface 930 mayinclude a network interface device or card, a modem, a router, a switch,a transceiver, and the like.

Second device 904 may include, for example, an input/output device 932.Input/output device 932 is representative of one or more devices orfeatures that may be configurable to accept or otherwise introduce humanor machine inputs, or one or more devices or features that may beconfigurable to deliver or otherwise provide for human or machineoutputs. By way of example but not limitation, input/output device 932may include an operatively configured display, speaker, keyboard, mouse,trackball, touch screen, data port, etc.

In a particular implementation, all or portions of actions or operationsset forth for process 600 may be executed by processing unit 920 basedon machine-readable instructions stored in memory 922. For exampleprocessing unit 920 may exchange control signaling with other entities(e.g. a standalone LSF, an integrated LSF, a base station or a UE) usingcommunication interface 930 in order to support actions of process 600.

Particular embodiments described herein relate to a non-transitorystorage medium comprising computer-readable instructions stored thereonwhich are executable by one or more processors of a location serverfunction associated with a radio access network for locating a userequipment (UE) to: exchange one or more first signaling messages withthe UE, the one or more first signaling messages comprising: (i) alocation measurement obtained by the UE, the location server functionenabled to determine a location estimate for the UE based at least inpart on the location measurement; (ii) a request sent to the UE for thelocation measurement; (iii) assistance data sent to the UE, theassistance data assisting the UE to obtain the location measurement; or(iv) a combination thereof; and exchange one or more second signalingmessages with a location server associated with a core network, the oneor more second signaling messages comprising location information forthe UE, a request for the location information for the UE, a locationconfiguration for the UE, a request for the location configuration forthe UE, a location context for the UE, a request for the locationcontext for the UE, or a combination thereof. In one particularimplementation, the one or more first signaling messages comprise one ormore layer 3 messages, and wherein the one or more second signalingmessages comprise one or more control plane messages or one or more userplane messages. In another particular implementation, the locationserver function associated with the radio access network is configuredto obtain an estimated location of the UE independently of the locationserver associated with the core network. In another particularimplementation, the location server function is integrated with a basestation or access point, or comprises a standalone entity. In anotherparticular implementation, the location server function comprises astandalone entity and the one or more first signaling messages isexchanged using an intermediate base station to transmit the one or morefirst signaling messages between the location server function and theUE, the one or more first signaling messages undergoing protocolconversion at the intermediate base station. In another particularimplementation, the one or more first signaling messages is exchanged inpart using a Fifth Generation (5G) radio interface or a 3^(rd)Generation Partnership Project (3GPP) New Radio (NR). In anotherparticular implementation, the location measurement comprises ameasurement of received signal strength indication (RSSI), measurementof angle of arrival (AOA), measurement of round trip signal propagationtime (RTT), measurement of reference signal time difference (RSTD),signal to noise ratio (S/N), reference signal received power (RSRP),reference signal received quality (RSRQ), measurement of code phase fora satellite vehicle (SV), a carrier phase for an SV or a locationestimate for the UE, or a combination thereof. In another particularimplementation, the assistance data is transmitted to the UE using abroadcast message. In another particular implementation, a locationestimate for the UE is obtained based at least in part on the locationmeasurement. In another particular implementation, the locationinformation comprises a location estimate for the UE or locationmeasurements for the UE, or a combination thereof. In another particularimplementation, the location configuration comprises parameters definingperiodic location estimation of the UE, triggered location estimation ofthe UE or location estimation accuracy for the UE, or a combinationthereof. In another particular implementation, the location contextcomprises a last known serving cell identifier (ID) for the UE, a lastknown serving base station ID for the UE, a last known location for theUE or the location measurement, or a combination thereof. In anotherparticular implementation, the one or more second signaling messages aredefined according to the Long Term Evolution (LTE) Positioning ProtocolAnnex (LPPa) protocol for the 3^(rd) Generation Partnership Project(3GPP). In another particular implementation, the one or more secondsignaling messages are exchanged using the Internet Protocol (IP).

Particular embodiments described herein relate to a location serverfunction associated with a radio access network for locating a userequipment (UE) comprising: means for exchanging one or more firstsignaling messages with the UE, the one or more first signaling messagescomprising: (i) a location measurement obtained by the UE, the locationserver function enabled to determine a location estimate for the UEbased at least in part on the location measurement; (ii) a request sentto the UE for the location measurement; (iii) assistance data sent tothe UE, the assistance data assisting the UE to obtain the locationmeasurement; or (iv) a combination thereof; and means for exchanging oneor more second signaling messages with a location server associated witha core network, the one or more second signaling messages comprisinglocation information for the UE, a request for the location informationfor the UE, a location configuration for the UE, a request for thelocation configuration for the UE, a location context for the UE, arequest for the location context for the UE, or a combination thereof.In one particular implementation, the one or more first signalingmessages comprise one or more layer 3 messages, and wherein the one ormore second signaling messages comprise one or more control planemessages or one or more user plane messages. In another particularimplementation, the location server function associated with the radioaccess network is configured to obtain an estimated location of the UEindependently of the location server associated with the core network.In another particular implementation, the location server function isintegrated with a base station or access point, or comprises astandalone entity. In another particular implementation, the locationserver function comprises a standalone entity and the one or more firstsignaling messages is exchanged using an intermediate base station totransmit the one or more first signaling messages between the locationserver function and the UE, the one or more first signaling messagesundergoing protocol conversion at the intermediate base station. Inanother particular implementation, the one or more first signalingmessages is exchanged in part using a Fifth Generation (5G) radiointerface or a 3^(rd) Generation Partnership Project (3GPP) New Radio(NR). In another particular implementation, the location measurementcomprises a measurement of received signal strength indication (RSSI),measurement of angle of arrival (AOA), measurement of round trip signalpropagation time (RTT), measurement of reference signal time difference(RSTD), signal to noise ratio (S/N), reference signal received power(RSRP), reference signal received quality (RSRQ), measurement of codephase for a satellite vehicle (SV), a carrier phase for an SV or alocation estimate for the UE, or a combination thereof. In anotherparticular implementation, the assistance data is transmitted to the UEusing a broadcast message. In another particular implementation, alocation estimate for the UE is obtained based at least in part on thelocation measurement. In another particular implementation, the locationinformation comprises a location estimate for the UE or locationmeasurements for the UE, or a combination thereof. In another particularimplementation, the location configuration comprises parameters definingperiodic location estimation of the UE, triggered location estimation ofthe UE or location estimation accuracy for the UE, or a combinationthereof. In another particular implementation, the location contextcomprises a last known serving cell identifier (ID) for the UE, a lastknown serving base station ID for the UE, a last known location for theUE or the location measurement, or a combination thereof. In anotherparticular implementation, the one or more second signaling messages aredefined according to the Long Term Evolution (LTE) Positioning ProtocolAnnex (LPPa) protocol for the 3^(rd) Generation Partnership Project(3GPP). In another particular implementation, the one or more secondsignaling messages are exchanged using the Internet Protocol (IP).

Particular embodiments described herein relate to a non-transitorystorage medium comprising computer-readable instructions stored thereonwhich are executable by one or more processors of method of at a userequipment (UE) supporting location services to: exchange one or morefirst signaling messages with a location server function associated witha radio access network, the one or more first signaling messagescomprising: (i) a first location measurement obtained by the UE, thelocation server function enabled to determine an estimate location ofthe UE based at least in part on the first location measurement; (ii) arequest received by the UE for the first location measurement; (iii)first assistance data received by the UE, the first assistance dataassisting the UE to obtain the first location measurement; or (iv) acombination thereof; and exchange one or more second signaling messageswith a location server associated with a core network, the one or moresecond signaling message comprising a second location measurementobtained by the UE, a request received by the UE for the second locationmeasurement, second assistance data received by the UE, the secondassistance data assisting the UE to obtain the second locationmeasurement, or a combination thereof. In one particular implementation,the one or more first messages comprise one or more one or more layer 3messages, and wherein the one or more second signaling messages compriseone or more control plane messages or one or more user plane messages.In another particular implementation, the location server functioncomprises a base station, access point, or a standalone entity. Inanother particular implementation, the location server functioncomprises a standalone entity and one or more first signaling messagesis exchanged using an intermediate base station, one or more firstsignaling messages undergoing protocol conversion at the intermediatebase station. In another particular implementation, the one or morefirst signaling messages is exchanged in part using a Fifth Generation(5G) radio interface or a 3^(rd) Generation Partnership Project (3GPP)New Radio (NR). In another particular implementation, at least one ofthe first location measurement and the second location measurement is ameasurement of received signal strength indication (RSSI), angle ofarrival (AOA), round trip signal propagation time (RTT), referencesignal time difference (RSTD), signal to noise ratio (S/N), referencesignal received power (RSRP), reference signal received quality (RSRQ),a code phase for a satellite vehicle (SV), a carrier phase for an SV ora location estimate for the UE. In another particular implementation,the first assistance data is received by the UE by receiving a broadcastsignal. In another particular implementation, one or more secondsignaling messages are defined according to the Long Term Evolution(LTE) Positioning Protocol (LPP) protocol for the 3^(rd) GenerationPartnership Project (3GPP), the LPP Extensions (LPPe) protocol definedby the Open Mobile Alliance (OMA), or both LPP and LPPe.

Particular embodiments described herein relate to a user equipment (UE)supporting location services comprising: means for exchanging one ormore first signaling messages with a location server function associatedwith a radio access network, the one or more first signaling messagescomprising: (i) a first location measurement obtained by the UE, thelocation server function enabled to determine an estimate location ofthe UE based at least in part on the first location measurement; (ii) arequest received by the UE for the first location measurement; (iii)first assistance data received by the UE, the first assistance dataassisting the UE to obtain the first location measurement; or (iv) acombination thereof; and means for exchanging one or more secondsignaling messages with a location server associated with a corenetwork, the one or more second signaling message comprising a secondlocation measurement obtained by the UE, a request received by the UEfor the second location measurement, second assistance data received bythe UE, the second assistance data assisting the UE to obtain the secondlocation measurement, or a combination thereof. In one particularimplementation, the one or more first messages comprise one or more oneor more layer 3 messages, and wherein the one or more second signalingmessages comprise one or more control plane messages or one or more userplane messages. In another particular implementation, the locationserver function comprises a base station, access point, or a standaloneentity. In another particular implementation, the location serverfunction comprises a standalone entity and one or more first signalingmessages is exchanged using an intermediate base station, one or morefirst signaling messages undergoing protocol conversion at theintermediate base station. In another particular implementation, the oneor more first signaling messages is exchanged in part using a FifthGeneration (5G) radio interface or a 3^(rd) Generation PartnershipProject (3GPP) New Radio (NR). In another particular implementation, atleast one of the first location measurement and the second locationmeasurement is a measurement of received signal strength indication(RSSI), angle of arrival (AOA), round trip signal propagation time(RTT), reference signal time difference (RSTD), signal to noise ratio(S/N), reference signal received power (RSRP), reference signal receivedquality (RSRQ), a code phase for a satellite vehicle (SV), a carrierphase for an SV or a location estimate for the UE. In another particularimplementation, the first assistance data is received by the UE byreceiving a broadcast signal. In another particular implementation, oneor more second signaling messages are defined according to the Long TermEvolution (LTE) Positioning Protocol (LPP) protocol for the 3^(rd)Generation Partnership Project (3GPP), the LPP Extensions (LPPe)protocol defined by the Open Mobile Alliance (OMA), or both LPP andLPPe.

Particular embodiments described herein relate to a method of locating auser equipment (UE) at a location server associated with a core network,comprising: exchanging one or more first signaling messages with the UE,the one or more first signaling messages comprising a locationmeasurement received obtained by the UE, a request sent to the UE forthe location measurement, assistance data sent to the UE, the assistancedata assisting the UE to obtain the location measurement, or acombination thereof; and exchanging one or more second signalingmessages with a location server function associated with a radio accessnetwork, one or more second signaling message comprising locationinformation for the UE, a request for the location information for theUE, a location configuration for the UE, a request for the locationconfiguration for the UE, a location context for the UE, a request forthe location context for the UE, or a combination thereof. In oneparticular implementation, the one or more second signaling messagescomprise one or more control plane messages or one or more user planemessages. In another particular implementation, the location serverfunction comprises a base station, access point, or a standalone entity.In another particular implementation, one or more first signalingmessages is exchanged in part using a Fifth Generation (5G) radiointerface or a 3^(rd) Generation Partnership Project (3GPP) New Radio(NR). In another particular implementation, the location measurement isa measurement of received signal strength indication (RSSI), angle ofarrival (AOA), round trip signal propagation time (RTT), referencesignal time difference (RSTD), signal to noise ratio (S/N), referencesignal received power (RSRP), reference signal received quality (RSRQ),a code phase for a satellite vehicle (SV), a carrier phase for an SV, ora location estimate for the UE. In another particular implementation,the location estimate for the UE is obtained based at least in part onthe location measurement, the location information or both. In anotherparticular implementation, one or more first signaling messages aredefined according to the Long Term Evolution (LTE) Positioning Protocol(LPP) protocol for the 3^(rd) Generation Partnership Project (3GPP) theLPP Extensions (LPPe) protocol defined by the Open Mobile Alliance(OMA), or both LPP and LPPe. In another particular implementation, thelocation information comprises a location estimate for the UE, locationmeasurements for the UE or both. In another particular implementation,the location configuration comprises parameters defining periodiclocation of the UE, triggered location of the UE, location accuracy forthe UE, or a combination thereof. In another particular implementation,the location context comprises a last known serving cell identifier (ID)for the UE, a last known serving base station ID for the UE, a lastknown location for the UE, the location measurement, the locationinformation, or a combination thereof. In another particularimplementation, one or more second signaling messages are definedaccording to the Long Term Evolution (LTE) Positioning Protocol Annex(LPPa) protocol for the 3^(rd) Generation Partnership Project (3GPP). Inanother particular implementation, one or more second signaling messagesare exchanged using the Internet Protocol (IP).

Particular embodiments described herein further relate to a locationserver associated with a core network for locating a user equipment(UE), comprising: a communication interface; and one or more processorsto: exchange one or more first signaling messages through thecommunication interface with the UE, the one or more first signalingmessages comprising a location measurement received obtained by the UE,a request sent to the UE for the location measurement, assistance datasent to the UE, the assistance data assisting the UE to obtain thelocation measurement, or a combination thereof; and exchange one or moresecond signaling messages through the communication interface with alocation server function associated with a radio access network, one ormore second signaling message comprising location information for theUE, a request for the location information for the UE, a locationconfiguration for the UE, a request for the location configuration forthe UE, a location context for the UE, a request for the locationcontext for the UE, or a combination thereof. In one particularimplementation, the one or more second signaling messages comprise oneor more control plane messages or one or more user plane messages. Inanother particular implementation, the location server functioncomprises a base station, access point, or a standalone entity. Inanother particular implementation, one or more first signaling messagesis exchanged in part using a Fifth Generation (5G) radio interface or a3^(rd) Generation Partnership Project (3GPP) New Radio (NR). In anotherparticular implementation, the location measurement is a measurement ofreceived signal strength indication (RSSI), angle of arrival (AOA),round trip signal propagation time (RTT), reference signal timedifference (RSTD), signal to noise ratio (S/N), reference signalreceived power (RSRP), reference signal received quality (RSRQ), a codephase for a satellite vehicle (SV), a carrier phase for an SV, or alocation estimate for the UE. In another particular implementation, thelocation estimate for the UE is obtained based at least in part on thelocation measurement, the location information or both. In anotherparticular implementation, one or more first signaling messages aredefined according to the Long Term Evolution (LTE) Positioning Protocol(LPP) protocol for the 3^(rd) Generation Partnership Project (3GPP) theLPP Extensions (LPPe) protocol defined by the Open Mobile Alliance(OMA), or both LPP and LPPe. In another particular implementation, thelocation information comprises a location estimate for the UE, locationmeasurements for the UE or both. In another particular implementation,the location configuration comprises parameters defining periodiclocation of the UE, triggered location of the UE, location accuracy forthe UE, or a combination thereof. In another particular implementation,the location context comprises a last known serving cell identifier (ID)for the UE, a last known serving base station ID for the UE, a lastknown location for the UE, the location measurement, the locationinformation, or a combination thereof. In another particularimplementation, one or more second signaling messages are definedaccording to the Long Term Evolution (LTE) Positioning Protocol Annex(LPPa) protocol for the 3^(rd) Generation Partnership Project (3GPP). Inanother particular implementation, one or more second signaling messagesare exchanged using the Internet Protocol (IP).

Particular embodiments described herein further relate to anon-transitory storage medium comprising computer-readable instructionsstored thereon which are executable by one or more processors of alocation server associated with a core network for locating a userequipment (UE) to: exchange one or more first signaling messages withthe UE, the one or more first signaling messages comprising a locationmeasurement received obtained by the UE, a request sent to the UE forthe location measurement, assistance data sent to the UE, the assistancedata assisting the UE to obtain the location measurement, or acombination thereof; exchange a plurality of one or more secondsignaling messages with a location server function associated with aradio access network, one or more second signaling message comprisinglocation information for the UE, a request for the location informationfor the UE, a location configuration for the UE, a request for thelocation configuration for the UE, a location context for the UE, arequest for the location context for the UE, or a combination thereof.In one particular implementation, the one or more second signalingmessages comprise one or more control plane messages or one or more userplane messages. In another particular implementation, the locationserver function comprises a base station, access point, or a standaloneentity. In another particular implementation, one or more firstsignaling messages is exchanged in part using a Fifth Generation (5G)radio interface or a 3^(rd) Generation Partnership Project (3GPP) NewRadio (NR). In another particular implementation, the locationmeasurement is a measurement of received signal strength indication(RSSI), angle of arrival (AOA), round trip signal propagation time(RTT), reference signal time difference (RSTD), signal to noise ratio(S/N), reference signal received power (RSRP), reference signal receivedquality (RSRQ), a code phase for a satellite vehicle (SV), a carrierphase for an SV, or a location estimate for the UE. In anotherparticular implementation, the location estimate for the UE is obtainedbased at least in part on the location measurement, the locationinformation or both. In another particular implementation, one or morefirst signaling messages are defined according to the Long TermEvolution (LTE) Positioning Protocol (LPP) protocol for the 3^(rd)Generation Partnership Project (3GPP) the LPP Extensions (LPPe) protocoldefined by the Open Mobile Alliance (OMA), or both LPP and LPPe. Inanother particular implementation, the location information comprises alocation estimate for the UE, location measurements for the UE or both.In another particular implementation, the location configurationcomprises parameters defining periodic location of the UE, triggeredlocation of the UE, location accuracy for the UE, or a combinationthereof. In another particular implementation, the location contextcomprises a last known serving cell identifier (ID) for the UE, a lastknown serving base station ID for the UE, a last known location for theUE, the location measurement, the location information, or a combinationthereof. In another particular implementation, one or more secondsignaling messages are defined according to the Long Term Evolution(LTE) Positioning Protocol Annex (LPPa) protocol for the 3^(rd)Generation Partnership Project (3GPP). In another particularimplementation, one or more second signaling messages are exchangedusing the Internet Protocol (IP).

Particular embodiments described herein further relate to A locationserver associated with a core network for locating a user equipment(UE), comprising: means for exchanging a one or more first signalingmessages with the UE, the one or more first signaling messagescomprising a location measurement received obtained by the UE, a requestsent to the UE for the location measurement, assistance data sent to theUE, the assistance data assisting the UE to obtain the locationmeasurement, or a combination thereof; means for exchanging a pluralityof one or more second signaling messages with a location server functionassociated with a radio access network, one or more second signalingmessage comprising location information for the UE, a request for thelocation information for the UE, a location configuration for the UE, arequest for the location configuration for the UE, a location contextfor the UE, a request for the location context for the UE, or acombination thereof. In one particular implementation, the one or moresecond signaling messages comprise one or more control plane messages orone or more user plane messages. In another particular implementation,the location server function comprises a base station, access point, ora standalone entity. In another particular implementation, one or morefirst signaling messages is exchanged in part using a Fifth Generation(5G) radio interface or a 3^(rd) Generation Partnership Project (3GPP)New Radio (NR). In another particular implementation, the locationmeasurement is a measurement of received signal strength indication(RSSI), angle of arrival (AOA), round trip signal propagation time(RTT), reference signal time difference (RSTD), signal to noise ratio(S/N), reference signal received power (RSRP), reference signal receivedquality (RSRQ), a code phase for a satellite vehicle (SV), a carrierphase for an SV, or a location estimate for the UE. In anotherparticular implementation, the location estimate for the UE is obtainedbased at least in part on the location measurement, the locationinformation or both. In another particular implementation, one or morefirst signaling messages are defined according to the Long TermEvolution (LTE) Positioning Protocol (LPP) protocol for the 3^(rd)Generation Partnership Project (3GPP) the LPP Extensions (LPPe) protocoldefined by the Open Mobile Alliance (OMA), or both LPP and LPPe. Inanother particular implementation, the location information comprises alocation estimate for the UE, location measurements for the UE or both.In another particular implementation, the location configurationcomprises parameters defining periodic location of the UE, triggeredlocation of the UE, location accuracy for the UE, or a combinationthereof. In another particular implementation, the location contextcomprises a last known serving cell identifier (ID) for the UE, a lastknown serving base station ID for the UE, a last known location for theUE, the location measurement, the location information, or a combinationthereof. In another particular implementation, one or more secondsignaling messages are defined according to the Long Term Evolution(LTE) Positioning Protocol Annex (LPPa) protocol for the 3^(rd)Generation Partnership Project (3GPP). In another particularimplementation, one or more second signaling messages are exchangedusing the Internet Protocol (IP).

As used herein, the terms “mobile device” and “user equipment” (UE) areused synonymously to refer to a device that may from time to time have alocation that changes. The changes in location may comprise changes todirection, distance, orientation, etc., as a few examples. In particularexamples, a mobile device may comprise a cellular telephone, wirelesscommunication device, user equipment, laptop computer, other personalcommunication system (PCS) device, personal digital assistant (PDA),personal audio device (PAD), portable navigational device, and/or otherportable communication devices. A mobile device may also comprise aprocessor and/or computing platform adapted to perform functionscontrolled by machine-readable instructions.

The methodologies described herein may be implemented by various meansdepending upon applications according to particular examples. Forexample, such methodologies may be implemented in hardware, firmware,software, or combinations thereof. In a hardware implementation, forexample, a processing unit may be implemented within one or moreapplication specific integrated circuits (ASICs), digital signalprocessors (DSPs), digital signal processing devices (DSPDs),programmable logic devices (PLDs), field programmable gate arrays(FPGAs), processors, controllers, micro-controllers, microprocessors,electronic devices, other devices units designed to perform thefunctions described herein, or combinations thereof.

“Instructions” as referred to herein relate to expressions whichrepresent one or more logical operations. For example, instructions maybe “machine-readable” by being interpretable by a machine for executingone or more operations on one or more data objects. However, this ismerely an example of instructions and claimed subject matter is notlimited in this respect. In another example, instructions as referred toherein may relate to encoded commands which are executable by aprocessing circuit having a command set which includes the encodedcommands. Such an instruction may be encoded in the form of a machinelanguage understood by the processing circuit. Again, these are merelyexamples of an instruction and claimed subject matter is not limited inthis respect.

“Storage medium” as referred to herein relates to media capable ofmaintaining expressions which are perceivable by one or more machines.For example, a storage medium may comprise one or more storage devicesfor storing machine-readable instructions or information. Such storagedevices may comprise any one of several media types including, forexample, magnetic, optical or semiconductor storage media. Such storagedevices may also comprise any type of long term, short term, volatile ornon-volatile memory devices. However, these are merely examples of astorage medium, and claimed subject matter is not limited in theserespects.

Some portions of the detailed description included herein are presentedin terms of algorithms or symbolic representations of operations onbinary digital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular operations pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals, or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the discussion herein, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer or a similar special purpose electronic computingdevice. In the context of this specification, therefore, a specialpurpose computer or a similar special purpose electronic computingdevice is capable of manipulating or transforming signals, typicallyrepresented as physical electronic or magnetic quantities withinmemories, registers, or other information storage devices, transmissiondevices, or display devices of the special purpose computer or similarspecial purpose electronic computing device.

Wireless communication techniques described herein may be in connectionwith various wireless communications networks such as a wireless widearea network (WWAN), a wireless local area network (WLAN), a wirelesspersonal area network (WPAN), and so on. The term “network” and “system”may be used interchangeably herein. A WWAN may be a Code DivisionMultiple Access (CDMA) network, a Time Division Multiple Access (TDMA)network, a Frequency Division Multiple Access (FDMA) network, anOrthogonal Frequency Division Multiple Access (OFDMA) network, aSingle-Carrier Frequency Division Multiple Access (SC-FDMA) network, orany combination of the above networks, and so on. A CDMA network mayimplement one or more radio access technologies (RATs) such as cdma2000,Wideband CDMA (WCDMA), to name just a few radio technologies. Here,cdma2000 may include technologies implemented according to IS-95,IS-2000, and IS-856 standards. A TDMA network may implement GlobalSystem for Mobile Communications (GSM), Digital Advanced Mobile PhoneSystem (D-AMPS), or some other RAT. GSM and WCDMA are described indocuments from a consortium named “3rd Generation Partnership Project”(3GPP). Cdma2000 is described in documents from a consortium named “3rdGeneration Partnership Project 2” (3GPP2). 3GPP and 3GPP2 documents arepublicly available. 4G Long Term Evolution (LTE) and 5G or New Radio(NR) communications networks may also be implemented in accordance withclaimed subject matter, in an aspect. A WLAN may comprise an IEEE802.11x network, and a WPAN may comprise a Bluetooth network, an IEEE802.15x, for example. Wireless communication implementations describedherein may also be used in connection with any combination of WWAN, WLANor WPAN.

In another aspect, as previously mentioned, a wireless transmitter oraccess point may comprise a femtocell, utilized to extend cellulartelephone service into a business or home. In such an implementation,one or more mobile devices may communicate with a femtocell via a codedivision multiple access (CDMA) cellular communication protocol, forexample, and the femtocell may provide the mobile device access to alarger cellular telecommunication network by way of another broadbandnetwork such as the Internet.

The terms, “and,” and “or” as used herein may include a variety ofmeanings that will depend at least in part upon the context in which itis used. Typically, “or” if used to associate a list, such as A, B or C,is intended to mean A, B, and C, here used in the inclusive sense, aswell as A, B or C, here used in the exclusive sense. Referencethroughout this specification to “one example” or “an example” meansthat a particular feature, structure, or characteristic described inconnection with the example is included in at least one example ofclaimed subject matter. Thus, the appearances of the phrase “in oneexample” or “an example” in various places throughout this specificationare not necessarily all referring to the same example. Furthermore, theparticular features, structures, or characteristics may be combined inone or more examples. Examples described herein may include machines,devices, engines, or apparatuses that operate using digital signals.Such signals may comprise electronic signals, optical signals,electromagnetic signals, or any form of energy that provides informationbetween locations.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein. Therefore, it isintended that claimed subject matter not be limited to the particularexamples disclosed, but that such claimed subject matter may alsoinclude all aspects falling within the scope of the appended claims, andequivalents thereof.

What is claimed is:
 1. A method of locating a user equipment (UE) at alocation server associated with a radio access network, the methodcomprising: exchanging one or more first signaling messages with the UE,the one or more first signaling messages comprising: (i) a locationmeasurement obtained by the UE, the location server associated with theradio access network enabled to determine a location estimate for the UEbased at least in part on the location measurement; or (ii) a requestsent to the UE for the location measurement; or (iii) a combinationthereof; and exchanging one or more second signaling messages with alocation server associated with a core network, the one or more secondsignaling messages comprising a location configuration for the UE, or arequest for the location configuration for the UE, or a location contextfor the UE, or a request for the location context for the UE, or acombination of two or more thereof, wherein the location configurationfor the UE comprises one or more parameters indicative of one or moreconditions or one or more events under which one or more operations oractions supporting determination of an estimated location of the UE isto occur, wherein the location context for the UE comprises one or moreparameters characterizing a current location of the UE and one or morepast locations of the UE, and wherein the location server associatedwith the radio access network is integrated with a base station or anaccess point.
 2. The method of claim 1, wherein the one or more firstsignaling messages comprise one or more layer 3 messages, and whereinthe one or more second signaling messages comprise one or more controlplane messages or one or more user plane messages.
 3. The method ofclaim 1, wherein the location server associated with the radio accessnetwork is configured to obtain the location estimate for the UEindependently of the location server associated with the core network.4. The method of claim 1, wherein the one or more first signalingmessages are exchanged in part using a Fifth Generation (5G) radiointerface or a 3^(rd) Generation Partnership Project (3GPP) New Radio(NR).
 5. The method of claim 1, wherein the location measurementcomprises a measurement of received signal strength indication (RSSI),measurement of angle of arrival (AOA), measurement of round trip signalpropagation time (RTT), measurement of reference signal time difference(RSTD), signal to noise ratio (S/N), reference signal received power(RSRP), reference signal received quality (RSRQ), measurement of codephase for a satellite vehicle (SV), a carrier phase for an SV or alocation estimate for the UE, or a combination thereof.
 6. The method ofclaim 1, wherein assistance data is transmitted to the UE using abroadcast message.
 7. The method of claim 1, further comprisingobtaining a location estimate for the UE based at least in part on thelocation measurement.
 8. The method of claim 1, wherein the locationinformation comprises a location estimate for the UE or locationmeasurements for the UE, or a combination thereof.
 9. The method ofclaim 1, wherein the location configuration comprises parametersdefining periodic location estimation of the UE, triggered locationestimation of the UE or location estimation accuracy for the UE, or acombination thereof.
 10. The method of claim 1, wherein the locationcontext comprises a last known serving cell identifier (ID) for the UE,a last known serving base station ID for the UE, a last known locationfor the UE or the location measurement, or a combination thereof. 11.The method of claim 1, wherein the one or more second signaling messagesare defined according to Long Term Evolution (LTE) Positioning ProtocolAnnex (LPPa) protocol for the 3^(rd) Generation Partnership Project(3GPP).
 12. The method of claim 1, wherein the one or more secondsignaling messages are exchanged using Internet Protocol (IP).
 13. Alocation server associated with a radio access network for locating auser equipment (UE), the location server comprising: a communicationinterface to transmit and receive signaling messages; and one or moreprocessors configured to exchange one or more first signaling messageswith the UE through the communication interface, the one or more firstsignaling messages comprising: (i) a location measurement obtained bythe UE, the location server enabled to determine a location estimate forthe UE based at least in part on the location measurement; or (ii) arequest sent to the UE for the location measurement; or (iii) acombination thereof; and exchange one or more second signaling messageswith a location server associated with a core network through thecommunication interface, the one or more second signaling messagescomprising a location configuration for the UE, or a request for thelocation configuration for the UE, or a location context for the UE, ora request for the location context for the UE, or a combination of twoor more thereof, wherein the location configuration for the UE comprisesone or more parameters indicative of one or more conditions or one ormore events under which one or more operations or actions supportingdetermination of an estimated location of the UE is to occur, whereinthe location context for the UE comprises one or more parameterscharacterizing a current location of the UE and one or more pastlocations of the UE, and wherein the location server associated with theradio access network is integrated with a base station or an accesspoint.
 14. The location server of claim 13, wherein the one or morefirst signaling messages are exchanged in part using a Fifth Generation(5G) radio interface or a 3^(rd) Generation Partnership Project (3GPP)New Radio (NR).
 15. The location server of claim 13, wherein thelocation measurement comprises a measurement of received signal strengthindication (RSSI), measurement of angle of arrival (AOA), measurement ofround trip signal propagation time (RTT), measurement of referencesignal time difference (RSTD), signal to noise ratio (S/N), referencesignal received power (RSRP), reference signal received quality (RSRQ),measurement of code phase for a satellite vehicle (SV), a carrier phasefor an SV or a location estimate for the UE, or a combination thereof.16. A location server associated with a radio access network forlocating a user equipment (UE), comprising: means for exchanging one ormore first signaling messages with the UE, the one or more firstsignaling messages comprising: (i) a location measurement obtained bythe UE, the location server associated with the radio access networkenabled to determine a location estimate for the UE based at least inpart on the location measurement; or (ii) a request sent to the UE forthe location measurement; or (iii) a combination thereof; and means forexchanging one or more second signaling messages with a location serverassociated with a core network, the one or more second signalingmessages comprising a location configuration for the UE, or a requestfor the location configuration for the UE, or a location context for theUE, or a request for the location context for the UE, or a combinationof two or more thereof, wherein the location configuration for the UEcomprises one or more parameters indicative of one or more conditions orone or more events under which one or more operations or actionssupporting determination of an estimated location of the UE is to occur,wherein the location context for the UE comprises one or more parameterscharacterizing a current location of the UE and one or more pastlocations of the UE, and wherein the location server associated with theradio access network is integrated with a base station or an accesspoint.
 17. The location server of claim 16, wherein the one or morefirst signaling messages are to be exchanged in part using a FifthGeneration (5G) radio interface or a 3^(rd) Generation PartnershipProject (3GPP) New Radio (NR).
 18. The location server of claim 16,wherein the location measurement comprises a measurement of receivedsignal strength indication (RSSI), measurement of angle of arrival(AOA), measurement of round trip signal propagation time (RTT),measurement of reference signal time difference (RSTD), signal to noiseratio (S/N), reference signal received power (RSRP), reference signalreceived quality (RSRQ), measurement of code phase for a satellitevehicle (SV), a carrier phase for an SV or a location estimate for theUE, or a combination thereof.
 19. An article comprising: anon-transitory computer-readable medium comprising machine-readableinstructions stored thereon which are executable by a processor of alocation server associated with a radio access network to: initiateexchange of one or more first signaling messages with a user equipment(UE), the one or more first signaling messages comprising: (i) alocation measurement obtained by the UE, the location server associatedwith the radio access network enabled to determine a location estimatefor the UE based at least in part on the location measurement; or (ii) arequest sent to the UE for the location measurement; or (iii) acombination thereof; and initiate exchange of one or more secondsignaling messages with a location server associated with a corenetwork, the one or more second signaling messages comprising a locationconfiguration for the UE, or a request for the location configurationfor the UE, or a location context for the UE, or a request for thelocation context for the UE, or a combination of two or more thereof,wherein the location configuration for the UE comprises one or moreparameters indicative of one or more conditions or one or more eventsunder which one or more operations or actions supporting determinationof an estimated location of the UE is to occur, wherein the locationcontext for the UE comprises one or more parameters characterizing acurrent location of the UE and one or more past locations of the UE, andwherein the location server associated with the radio access network isintegrated with a base station or an access point.
 20. The article ofclaim 19, wherein the one or more first signaling messages comprise oneor more layer 3 messages, and wherein the one or more second signalingmessages comprise one or more control plane messages or one or more userplane messages.
 21. The article of claim 19, wherein themachine-readable instructions are further executable by the processor toexchange the one or more first signaling messages in part using a FifthGeneration (5G) radio interface or a 3^(rd) Generation PartnershipProject (3GPP) New Radio (NR).
 22. The article of claim 19, wherein thelocation measurement comprises a measurement of received signal strengthindication (RSSI), measurement of angle of arrival (AOA), measurement ofround trip signal propagation time (RTT), measurement of referencesignal time difference (RSTD), signal to noise ratio (S/N), referencesignal received power (RSRP), reference signal received quality (RSRQ),measurement of code phase for a satellite vehicle (SV), a carrier phasefor an SV or a location estimate for the UE, or a combination thereof.23. The method of claim 1, further comprising: broadcasting, prior toexchanging the one or more first signaling messages with the UE,assistance data to assist the UE to obtain the location measurement. 24.The method claim 23, further comprising: ciphering the assistance dataprior to broadcasting the assistance data.